Re: [Freedos-kernel] kernel 2034rc for testing
Hi! 15--2004 01:16 [EMAIL PROTECTED] (Bernd Blaauw) wrote to [EMAIL PROTECTED]: page, previous time I don't found it (if it was present). Also, when planned 2034 release? May be I wait this release and download it completely (instead patch), if it will be soon? BB the idea is to test *before* spreading to the general public. Of course, but I (yet?) have no (general purpose) test plan for kernel, I may test only requested area. BB I include this 2034 kernel in the next FreeDOS distribution, next Sunday. BB there have been a few times where a kernel was released, and a few days BB later a new kernel followed it because a larger public found a few bugs. :) Kernel shoul be re-release slightly often and it number should be function of release date. With this, quick re-releases shouldn't be a problem. :) --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] kernel 2034rc for testing
On Thu, 15 Apr 2004, Arkady V.Belousov wrote: BB I include this 2034 kernel in the next FreeDOS distribution, next Sunday. BB there have been a few times where a kernel was released, and a few days BB later a new kernel followed it because a larger public found a few bugs. :) Kernel shoul be re-release slightly often and it number should be function of release date. With this, quick re-releases shouldn't be a problem. :) kernel released when i like and with number i like keep in mind that proper release takes lot more time than simple daily tarball produced by cron job. besides general public will get just distributions so good sync this with bernd -- distribution (beta9) arent labelled date either basta --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel config.c,1.75,1.76 config.h,1.3,1.4 kernel.asm,1.50,1.51 main.c,1.70,1.71 segs.inc,1.17,1.18 task.c,1.40,1.41
On Tue, 13 Apr 2004, Arkady V.Belousov wrote:
13-áÐÒ-2004 11:54 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
+++ task.c13 Apr 2004 11:54:09 - 1.41
+ fstrcpy(Shell + strlen(Shell), MK_FP(FP_SEG(Config), Config-cfgInitTail));
endp = Shell + strlen(Shell);
fstrcpy(endp = Shell + strlen(Shell),
MK_FP(FP_SEG(Config), Config-cfgInitTail));
this won't work. We need the strlen of Shell after the fstrcpy. This is
really an fstrcat except that's not in asmsupt.asm.
endp = Shell + strlen(Shell) + strlen(Config-cfgInitTail);
fstrcpy(Shell + strlen(Shell), MK_FP(FP_SEG(Config), Config-cfgInitTail));
would work but I don't see the point.
STATIC VOID InitPgm(BYTE * pLine)
{
+ static char init[NAMEMAX];
+ static char inittail[NAMEMAX];
+
+ Config.cfgInit = init;
+ Config.cfgInitTail = inittail;
As I understand, these assignments may be performed statically.
Especially, if cfgInit and cfgInitTail fields will be moved out from Config
structure.
??? I don't understand what you mean here.
+ mov cx,-2 + init_end wrt INIT_TEXT ; word aligned
BTW, does (or not) NASM supports TASM/MASM compatible syntax:
mov cx,offset INIT_TEXT:init_end - 2 ; word aligned
NASM doesn't support offset.
Bart
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel config.c,1.75,1.76 config.h,1.3,1.4 kernel.asm,1.50,1.51 main.c,1.70,1.71 segs.inc,1.17,1.18 task.c,1.40,1.41
Hello Arkady, AVB Why? To make code more portable between assemblers. ROTFL tom --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel config.c,1.75,1.76 config.h,1.3,1.4 kernel.asm,1.50,1.51 main.c,1.70,1.71 segs.inc,1.17,1.18 task.c,1.40,1.41
Hi! 13--2004 19:58 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov [EMAIL PROTECTED]: AVB Why? To make code more portable between assemblers. te ROTFL ? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel config.c,1.75,1.76 config.h,1.3,1.4 kernel.asm,1.50,1.51 main.c,1.70,1.71 segs.inc,1.17,1.18 task.c,1.40,1.41
Hello Arkady, AVB Why? To make code more portable between assemblers. te ROTFL AVB ? Rolling On The Floor Laughing you really can't keep things untouched? I would really HATE the kernels assembly sources converted into GMOUSE cryptographic sources. tom --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel config.c,1.75,1.76 config.h,1.3,1.4 kernel.asm,1.50,1.51 main.c,1.70,1.71 segs.inc,1.17,1.18 task.c,1.40,1.41
Hi! 13--2004 20:30 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov [EMAIL PROTECTED]: AVB Why? To make code more portable between assemblers. te ROTFL te Rolling On The Floor Laughing te you really can't keep things untouched? See the difference: keep untouched or do so or so. Currently Bart actively _adds_ `wrt', so I ask if this is possible to use `:' instead `wrt'. te I would really HATE the kernels assembly sources converted into te GMOUSE cryptographic sources. :) --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel makefile,1.16,1.17
Hi! 12--2004 00:22 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: Forged to remove old INITHEADERS. Also, what bad in $(HDR)*.h, why enumerating .h files is better? BO It's not better as such, but I'm not sure if * works for all the different BO make tools we are using. It's safer. Don't sure about safer, but you may sometime forget to update manual list when something will be changed (renamed or added) in ../hdr. :) BO The same problem occurs with !ifdef -- esp Borland MAKE version 2.0. BO You might want to check out Turbo C 2.01 as our lowest common denominator BO compiler: BO http://community.borland.com/article/images/20841/tc201.zip BO it's 1074 KB. Ok, I try to download this. PPS: trailing spaces wasn't removed. :( BO Too many formatting changes make me tired when reading the diff... When $(CONFIGURATION) replaced by $(TARGET).lnk, changes anyway present. BO I don't see the point of changing :- to ::. Because I wish to make more clear difference between plain comments and commented commands. BO Similarly you still have too many optimizations which aren't. They are (usually) such for BC. Some changes I begin to check also with OW. BO For Watcom the code only becomes larger if you replace far pointers p-baz by BO explicit ((foo *)MK_FP(bar,0))-baz. BO Maybe if you use something like BO #if defined(__TURBOC__) (__TURBOC__ 0x202) BO #define para2far(seg) ((void _seg *)(seg)) Nice. Though: #if __TURBOC__ 0x202 /* by standard, non-defined names replaced by 0. */ /* if you worry, that __TURBOC__ may be empty definition: #define __TURBOC__ (and defined() doesn't saves in this case), you may use +0: #if __TURBOC__+0 0x202 */ # define FP_PTR(type,seg,ofs) ((type far*) MK_FP (seg, ofs)) # define FP_SEG_PTR(type,seg) ((type _seg*)(seg)) Explicit castings should ease to transit sources to C++ compilers. BO #else BO #define _seg far BO #define para2far(seg) (MK_FP(seg,0)) # define FP_PTR(type,seg,ofs) ((type far*) MK_FP (seg, ofs)) # define FP_SEG_PTR(type,seg) ((type far*) MK_FP (seg, 0)) BO #endif BO psp _seg *p = para2far(cu_psp); psp _seg *p = FP_SEG_PTR (psp, cu_psp); BTW, using such names as `psp', `seg' for types is misleading (looks like variable names). I think, `PSP' and `seg_t' in given case is better. BO r.es = FP_SEG(p-ps_filetab); BO r.di = FP_OFF(p-ps_filetab + bx); BO it will improve a bit and it's not too ugly. Fine. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel inithma.c,1.23,1.24 kernel.asm,1.47,1.48 main.c,1.69,1.70 segs.inc,1.16,1.17
Hi! 12--2004 00:30 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: in kernel.asm. Use std for the memory move: helps if there's overlap (PCs with a very low amount of RAM). +fmemcpy(HMADest, HMASource, len); _Standard_ memcpy() _doesn't_ handles memory overlapping. This does _only_ memmove(). BO our fmemcpy uses cld. It's fine for our use here now. There's either no BO overlap or it moves down. As you already explain in your comment above, there _may_ be overlap on PCs with a very low amount of RAM. So, if should guarantee/assume the enough memory space, or implement memmove(). BO This is deliberate. Guess I should add a comment -- the involved variables BO are aligned. Yes, good comments always welcomed. :) --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: generic.mak
Hi! 13--2004 02:06 Arkady V.Belousov wrote to [EMAIL PROTECTED]: AVB I test TC MAKE. Not funny image: TC MAKE doesn't support !ifndef, AVB WMAKED doesn't support $d(). BTW, just for information: TC compiles kernel (from scratch) in 3-4 minutes, BC - 8-9 minutes, OW - 17-25 minutes. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: batch and make files (description)
Hello Arkady, AVB PS4: repeat for my previous question: why to duplicate clean and AVB clobber? Another one: who make files status.me, *.cod, *.las? *.cod are generated by MSC, if compiled with 'generate assembly listing with source' (very handy when debugging) tom --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: batch and make files (description)
Hi! 8--2004 09:11 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov [EMAIL PROTECTED]: AVB PS4: repeat for my previous question: why to duplicate clean and AVB clobber? Another one: who make files status.me, *.cod, *.las? te *.cod are generated by MSC, if compiled with 'generate assembly te listing with source' (very handy when debugging) What about other files? I know that name status.me was used by (old version ? of) MultiEdit, about .las I can't suggest anything. PS: Currently I think how to optimize compilation process through making list of source files, which should be recompiled (and passing this list to compiler). Without this, (re)compilation by OW uses more than half of hour - starting of compiler is longer, than compilation itself. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: batch and make files
On Mon, 5 Apr 2004, Arkady V.Belousov wrote:
PS: config.h also may be removed, because it is dummy (for this only
required to remove reference in globals.h). When (and if!) it will be
required, it may be added back.
config.h contains
struct config { /* Configuration variables */
after Lucho's patch
PS2: kernel\nls\001-437.hc is desynced with kernel\nls_hc.asm.
It was accidentally checked into CVS as ascii instead of as binary, so I
had to correct that and fix the CRLF at the time (the .asm didn't change).
PS3: header files in globals.h and init-mode.h included in different order.
is that a problem?
PS4: repeat for my previous question: why to duplicate clean and
clobber? Another one: who make files status.me, *.cod, *.las?
ask Pat Villani. AFAICS clobber is a little more thorough than clean,
where clean removes enough to force a kernel rebuild, clobber tries to
remove all generated files (incl. kernel.sys).
Bart
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
On Mon, 5 Apr 2004 23:13:16 +0100 (BST), Bart Oldeman wrote:
Hi, in the FAQ, somebody claims that file handle 4 should default to
PRN:
http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/224
Any idea why this would work at all? And why it works in MS but not in
FreeDOS? Used language is C.
Look at the definitions in stdio.h - stdaux is _iob[3], and stdprn is
_iob[4] (Borland uses _streams instead of __iob). The order of these
devices in different in MS-DOS and FreeDOS:
MS-DOS: CON, AUX, PRN, CLOCK$, A:-D:, COM1, LPT1, LPT2, LPT3, CONFIG$,
COM2, COM3, COM4
FreeDOS: CON, PRN, AUX, LPT1, LPT2, COM1, COM2, COM3, COM4, CLOCK$,
A:-D:
Fortunately, fixing this is very easy. It's enough to swap the
corresponding entries in io.asm. Do I need to provide a patch for this?
Aren't you looking at the wrong place here? It's about the high level
handles as far as I know.
The PSP has for the handles:
0 1 2 3 4 5 6 ...
01 01 01 00 02 FF FF
01 = CON
00 = AUX
02 = PRN
which means that also in FreeDOS, (high level) handle 4 corresponds to
PRN.
So the problem must be somewhere else.
I don't understand you (I usually need a bit more explanation ;-) but
you're right! The follwing simple test program
#include stdio.h
void main()
{
fputc('\f', stdprn);
}
works on MS-DOS, FreeDOS before my patch, and FreeDOS after my patch!
So my patch is not needed then. And I have no idea what the bug reporter
means :-(
But today I encountered an application (a X-modem file transfer program
called TRANSFER.EXE by Datalight) that hangs up FreeDOS after returning to
DOS prompt when all my drivers and TSRs are loaded (and not in bare DOS).
This doesn't happen in MS-DOS (with the same TSRs and drivers). I need to
investigate where exactly the incompatibility is and then what exactly
causes the hang.
Lucho
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: batch and make files (description)
At least one of your emails was trapped by the SF mail system until I was able to free it this morning. Emails may not be over 40k in length, or else they are held until the list owner (me) accepts or rejects them (a manual process.) -jh Arkady V.Belousov wrote: Hi! [Don't know what happen, but SF silently ignores/losts my letters. B-E Second day: one was saturday, second was today. Not funny. Below _repost_ of my letter with new patch from today, monday.] New updates for my patches. Because I already remove intermediate files, there present diff file not to my last patch, but to files, as patched by Bart. - buildall.bat, clean.bat: not all DELs was NULed. - config.b: comment for NASM updated by request of Bernd. :) - kernel\makefile: not all individual rules was present (asmsupt.asm), not all dependencies was present (eg, segs.inc for irqstack.asm). - kernel\nls_load.c: removed. PS: config.h also may be removed, because it is dummy (for this only required to remove reference in globals.h). When (and if!) it will be required, it may be added back. PS2: kernel\nls\001-437.hc is desynced with kernel\nls_hc.asm. PS3: header files in globals.h and init-mode.h included in different order. PS4: repeat for my previous question: why to duplicate clean and clobber? Another one: who make files status.me, *.cod, *.las? -- _ This email message has been automatically encrypted using ROT-26. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
Hi, in the FAQ, somebody claims that file handle 4 should default to PRN: http://fd-doc.sourceforge.net/faq/cgi-bin/viewfaq.cgi?faq=incoming/224 Any idea why this would work at all? And why it works in MS but not in FreeDOS? Used language is C. Look at the definitions in stdio.h - stdaux is _iob[3], and stdprn is _iob[4] (Borland uses _streams instead of __iob). The order of these devices in different in MS-DOS and FreeDOS: MS-DOS: CON, AUX, PRN, CLOCK$, A:-D:, COM1, LPT1, LPT2, LPT3, CONFIG$, COM2, COM3, COM4 FreeDOS: CON, PRN, AUX, LPT1, LPT2, COM1, COM2, COM3, COM4, CLOCK$, A:-D: Fortunately, fixing this is very easy. It's enough to swap the corresponding entries in io.asm. Do I need to provide a patch for this? Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
MS-DOS: CON, AUX, PRN, CLOCK$, A:-D:, COM1, LPT1, LPT2, LPT3, CONFIG$, COM2, COM3, COM4 FreeDOS: CON, PRN, AUX, LPT1, LPT2, COM1, COM2, COM3, COM4, CLOCK$, A:-D: Fortunately, fixing this is very easy. It's enough to swap the corresponding entries in io.asm. Do I need to provide a patch for this? Here it is, below. Now stdaux and stdprn should work as in MS-DOS. Lucho --- io.asm 2003-06-15 16:21:26.0 +0200 +++ io.asm 2004-04-05 20:08:32.0 +0200 @@ -81,33 +81,33 @@ ; global _con_dev _con_devequ $ -dw _prn_dev,LGROUP +dw _aux_dev,LGROUP dw 8013h ; con device (stdin stdout) dw GenStrategy dw ConIntr db 'CON ' ; -; Generic prn device that can be redirected via mode -; -global _prn_dev -_prn_devdw _aux_dev,LGROUP -dw 0A040h -dw GenStrategy -dw PrnIntr -db 'PRN ' - -; ; Generic aux device that can be redirected via mode ; global _aux_dev -_aux_devdw _Lpt1Dev,LGROUP +_aux_devdw _prn_dev,LGROUP dw 8000h dw GenStrategy dw AuxIntr db 'AUX ' ; +; Generic prn device that can be redirected via mode +; +global _prn_dev +_prn_devdw _Lpt1Dev,LGROUP +dw 0A040h +dw GenStrategy +dw PrnIntr +db 'PRN ' + +; ; Printer device drivers ; _Lpt1Devdw _Lpt2Dev,LGROUP --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
Fortunately, fixing this is very easy. It's enough to swap the corresponding entries in io.asm. Do I need to provide a patch for this? Here it is, below. Now stdaux and stdprn should work as in MS-DOS. As always, a patched CVS kernel binary (FAT32, 80386, BC 4.52, aPack) is available in my ROMDSK binary package that can be downloaded at http://linux.tu-varna.acad.bg/~lig/romdsk/romd-bin.rar Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
Erwin Veermans schreef: Forbidden You don't have permission to access /~lig/romdsk/romd-bin.rar on this server. What am I doing wrong, or should I send some cigars first ? ;-) confirmed. do you compile from source or always work with binaries like I did? latest binary from Jeremy took a while so in a few spare hours on a Sunday afternoon I decided to finally learn how to compile. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
Forbidden You don't have permission to access /~lig/romdsk/romd-bin.rar on this server. confirmed. do you compile from source or always work with binaries like I did? Usually I work with the official kernel release (binary). But when time goes by and some interesting patches float by, I grab the daily (used to be nightly ?) kernel tar and compile it with OW. But now I was interested to see what Lucho's combination produced (386, BC, Apack) in terms of size. Erwin latest binary from Jeremy took a while so in a few spare hours on a Sunday afternoon I decided to finally learn how to compile. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] handle 4 defaulting to PRN???
Hi Eric, Eric Auer escribió: Hi, in the FAQ, somebody claims that file handle 4 should default to PRN: In my undersanding, handle 4 is stdprn (the other three being stdin, stdout, and stdaux, always using C's notation). So it shoulds sensible that it should point to PRN anyway, isn't it? Aitor --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: batch and make files
Hello Arkady, AVB I test batch and make files both under OW12 and BC31 would be great if you ewoild test them with TV 2.01 also (this is a reference compiler, BC31 not) btw: there is absolutely no need to mess with them - they usually work. tom --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patch: batch and make files
Arkady V.Belousov schreef: Hi! 4--2004 17:55 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov [EMAIL PROTECTED]: AVB I test batch and make files both under OW12 and BC31 te would be great if you ewoild ewoild=perform? would - 'if you would test them' te test them with TV 2.01 also (this is a reference compiler, BC31 not) How big is it? Where I may download it (without answering question and other scripting issues)? If it longer than 3M (www4mail limit), who may send it to me? te btw: there is absolutely no need to mess with them - they usually work. they=BC? It depends. :) 'they' = '(your changed) batchfiles' --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: FreeDOS idle HLT
On Mon, 29 Mar 2004 18:55:44 -0300, Alain wrote: New Power supplies are very cheap. For that they have simplified many important circuits. They don't handle current fluctuations vary well. Well, again from bad to worse... They must come with a BIG red sign HLT forbidden! then :-( Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
On Mon, 29 Mar 2004 19:00:54 -0300, Alain wrote: INHO and considering that FreeDOS is in C versus all other DOSes being in ASM ROM-DOS, our greatest living competitor (not speaking of the venerable DR-DOS that is still in coma and PC-DOS that must have finally died in 2002) is also written 90% in C but uses much more conventional RAM. But what we talk about is *data*, not code, so language doesn't matter. I believe that we should just _CELEBRATE_ :) FreeDOS 7.1: 10688 MS-DOS 7.1: 9680 PC-DOS 7.1: 9456 Where's the Champaigne? ;-) Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
On Fri, 26 Mar 2004 22:22:20 + (GMT), Bart Oldeman wrote: Can you check again? I think I solved at least Lucho's problem during the init phase -- when fnodes could overlap disk buffers! Weird things could happen indeed. Congratulations, Bart! Bug fixed indeed - just tried. But I keep thinking that the right place for the far fnodes is the HMA (I haven't checked yet your latest CVS changes though - you work lightning fast! ;-) By the way, you're a good detective (but in time you'll see that I'm also not a bad one ;-) Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel buildall.bat,1.3,1.4
On Sat, 27 Mar 2004, Arkady V.Belousov wrote: Batch file: __O\_/_\_/O__ @echo off ver/r set a=1 set b=if %%a%%== echo b set c=if not %%a%%== echo c %b% %c% _ O/~\ /~\O now try with set a= and for me it still echoed c. That was the problem. also try set d=echo %%a%% %d% Das war wohl Nix ;) Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
Hi! 27--2004 12:18 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: LG Bad news: the new build batch files don't do anything in 4DOS, probably BO it's picky about BO call config BO instead of BO call config.bat And? [BTW, just check under freecom - also all works.] PS: I not against of using explict extensions, but wonder what wrong in given case? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
Hi! 27--2004 21:10 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: Becuase I show in skipped part you, that this doesn't (always) works. BO that (not accepting call default.bat) is a bug in 4dos 6.02 then that call cls.com calls internal command both in NDOS and command.com also, so this is not a bug, but a feature. :( BO Personally I would like to compile the kernel without batch files using BO a simple make. Problem is that we're dealing with n incompatible MAKEs. Problem is same, as with shells - too many different and often incompatible ones. BO Also at the time Tom mentioned that he found batch files easier to debug. I agreed - MAKE execution (sometime) isn't completely transparent and it can't replace the shell: for example, what about conditional execution? Something like if exist file set var=path? BO * GNU Make is not shipped with FreeDOS, and the last time I checked it the BO 8086 version from GNUish wasn't terribly stable (could have been an FD BO kernel problem though) I wonder why, but (almost) all GNU tools executables are too big and not always available under DOS (especially 16-bit). :( BO * OW WMAKE also uses quite a bit of memory and can't swap. For BC I use MAKER -S (which I also add into config.b). --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patches
Hi! 26--2004 11:24 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: Bart, what wrong wit my latest patches for batch files and for sources? They are small and they are tested - which reason to silently reject them? BO not rejected, just haven't got around to look at them closely. Ok, I wait your comments. Don't drop them into trash silently. Also, batch files was sended month ago. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patches
On Fri, 26 Mar 2004, Arkady V.Belousov wrote: Hi! 26-íÁÒ-2004 19:33 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: And let me remind you two more bugs, which you don't fix yet: first one is in INT 21/6C (lost check for nonzero AL) BO that's not a bug, we discussed this before -- see Luchos reply This is bug. When Lucho says that this is patch from me, I quote him my letter where was _not_ sayed, that check for AL should be removed - there was discussed only checks for DL. That's a misunderstanding: Date: Mon, 2 Feb 2004 21:03:52 +0300 (MSK) From: Arkady V.Belousov [...] 2-æÅ×-2004 10:58 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to [EMAIL PROTECTED]: if ((lr.DL 0xef) 0x2) First, losted AL check (for AX=6C00) - should be if (lr.AL || ((lr.DL. LG You probably forgot about that. Check for AL=0 was deliberately removed! LG File history.txt says: * inthndlr.c: Remove AL=0 check for AH=6c (from Arkady) Optimize DL check. The (from Arkady) here refers to Optimize DL check. because it's stated like this: + Changes Lucho: * inthndlr.c: Remove AL=0 check for AH=6c (from Arkady) Optimize DL check. There really are DOS programs that use int21/ax=0x6c02 or something like that where they really mean to use extended open. This was discussed here around October last year. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
The patched kernel behaves very strangely! :-( It outputs an error for DEVICE=C:\DOS\HIRAM.EXE line and doesn't load it and repeates this with many other lines (but not all). For my simpler floppy configuration, it doesn't load HIMEM64.EXE without even showing an error! The current nightly-kernel may have reached a new landmark in the quest for smaller conventinal-memory footprint but it lost ground in usability and compatibility. My test-machines halt on various arbitrary points telling me: more than two near fnodes requested at the same time Can you check again? I think I solved at least Lucho's problem during the init phase -- when fnodes could overlap disk buffers! Weird things could happen indeed. After booting I haven't seen the message you quote though, so please let me know how to reproduce if it still occurs for you. I made an intermediate kernel tarball just in case the cronjob fails. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patches
Hi! 26--2004 22:09 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: This is bug. When Lucho says that this is patch from me, I quote him my letter where was _not_ sayed, that check for AL should be removed - there was discussed only checks for DL. BO That's a misunderstanding: BO BO Date: Mon, 2 Feb 2004 21:03:52 +0300 (MSK) BO From: Arkady V.Belousov BO 2--2004 10:58 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to BO [EMAIL PROTECTED]: if ((lr.DL 0xef) 0x2) First, losted AL check (for AX=6C00) - should be if (lr.AL || ((lr.DL. LG You probably forgot about that. Check for AL=0 was deliberately removed! LG File history.txt says: * inthndlr.c: Remove AL=0 check for AH=6c (from Arkady) Optimize DL check. BO BO The (from Arkady) here refers to Optimize DL check. I not see this from comment! I read this as Arkady removes AL=0 check and then DL check optimized! BO because it's stated like this: BO + Changes Lucho: BO * inthndlr.c: Remove AL=0 check for AH=6c (from Arkady) Optimize DL BO check. Then, at least, this should be rephrased or reformated. For example: * inthndlr.c: Remove AL=0 check for AH=6c. (from Arkady:) Optimize DL check. BO There really are DOS programs that use int21/ax=0x6c02 or something like BO that where they really mean to use extended open. This was discussed here BO around October last year. No, I not see at Topica this discussion. Probably, because I was at those time in bounce state? Well, just checked: yes, under MS-DOS 6.22 file created both with 0x6C00 and 0x6C02. Another bug in RBIL? :( --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patches
Hi! 26--2004 21:24 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to [EMAIL PROTECTED]: [...] bugs, which you don't fix yet: first one is in INT 21/6C (lost check for nonzero AL) LG I already wrote you: This is NOT a bug - What you wrote to me was: You probably forgot about that. Check for AL=0 was deliberately removed!. You not say that checking for AL is bug (in RBIL), whereas mention of me in history in this context forces me to suggest that this is because I not mention AL in my optimization. PS: Just checked TechHelp: it says nothing about AL, only AH=6C. Definitely bug in RBIL. :( --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] VDISK header
Hi! 26--2004 23:54 [EMAIL PROTECTED] (Bart Oldeman) wrote to [EMAIL PROTECTED]: AVB ; the HMA area is filled with 1eh+3(=sizeof VDISK) = 33 byte dummy data, AVB ; so nothing will ever be below 0x:0031 AVB begin_hma: AVB times 10h db 0 ; filler [:0..:10] AVB times 20h db 0 AVB db 0 BTW, strange arithmetics: sayed about 33 bytes, but allocated 49 bytes. Sorry, forget that :0 is not yet above first meg. But why not comment this explicitly: times 10h db 0 ; filler [:0..:10] times 21h db 0 ; VDISK header after first meg Also, where documented VDISK header (where I may read about this)? BO It's in the VCPI spec. Available at many places including here: BO www.dose.se/docs/osdoc/unsorted/ProtectedMode/VCPI.txt No, there sayed only about signature and showed how to copy word value from offset 0x1E. :( Other fields are unexplained. BO 49=33+16. The first 16 are still in the ROM BIOS. The header is at BO :0010 Yes, I see now, sorry for this silly forgiveness (though, there are not enough comments anyway). But why HMAOFFSET in inithma.c is 0x20, not 0x10 or 0x30? Also, what about moving VDISK header from inithma.c:InstallVDISK() to kernel.asm? This allows to remove InstallVDISK(). Also, for this HMAOFFSET in inithma.c should be defined as 0x10 and MoveKernel() should (unconditionally) adjust by this value src, dst and len: #define HMAOFFSET 0x10 HMASource = MK_FP(CurrentKernelSegment, (FP_OFF(_HMATextStart) -16) + HMAOFFSET); ^^^ HMADest = MK_FP(NewKernelSegment, HMAOFFSET); ^ len = ((FP_OFF(_HMATextEnd) - (FP_OFF(_HMATextStart) 0xfff0)) + HMAOFFSET + 15) -16; Also, as I say previously, most of reserved are (0x30 bytes) may be reused when kernel finally moved to low memory, by shifting segment of copied code by 0x30/0x10=3. (Of course, in this case MoveKernel() should adjust also offsets not by 0x10, but by 0x30; value of offset may be second argument of MoveKernel()). IF YOU WISH, I MAY DO (AND TEST) THIS MYSELF. What you think about this? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] VDISK header
Also, where documented VDISK header (where I may read about this)? BO It's in the VCPI spec. Available at many places including here: BO www.dose.se/docs/osdoc/unsorted/ProtectedMode/VCPI.txt No, there sayed only about signature and showed how to copy word value from offset 0x1E. :( Other fields are unexplained. it's a boot block. The rest (for a real VDISK) will be a normal BPB (pre DOS 3.0 so no hidden sectors DWORD). I am too tired now to answer the other questions :) Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] patches
On Sat, 27 Mar 2004 03:22:59 +0300 (MSK), Arkady V.Belousov wrote: PS: Just checked TechHelp: it says nothing about AL, only AH=6C. Definitely bug in RBIL. :( MS-DOS technical reference defines AL=0 as reserved (http://www.clipx.net/ng/dos5/ng1ff99.php). We already discussed this issue last year and I wouldn't like to comment on it further. Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
The patched kernel behaves very strangely! :-( It outputs an error for DEVICE=C:\DOS\HIRAM.EXE line and doesn't load it and repeates this with many other lines (but not all). For my simpler floppy configuration, it doesn't load HIMEM64.EXE without even showing an error! The current nightly-kernel may have reached a new landmark in the quest for smaller conventinal-memory footprint but it lost ground in usability and compatibility. My test-machines halt on various arbitrary points telling me: more than two near fnodes requested at the same time :-/ Erwin --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
The current nightly-kernel may have reached a new landmark in the quest for smaller conventinal-memory footprint but it lost ground in usability and compatibility. My test-machines halt on various arbitrary points telling me: more than two near fnodes requested at the same time ok that's good. It means that that panic was justified to implement for me as a failsafe. Remember CVS is for (public) development, released kernels should never have this behaviour so I'll have to fix something... Sure, not meant for end-users. I just figured it would be good to raise an alert about the current kernel to back up Lucho's remark. Bart Erwin --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] new conv mem highs.
The current nightly-kernel may have reached a new landmark in the quest for smaller conventinal-memory footprint but it lost ground in usability and compatibility. My test-machines halt on various arbitrary points telling me: more than two near fnodes requested at the same time if files=10 would work for you, then there are 10 of those f-nodes. maybe that's the minimum that should be kept in conventional memory? move all i-nodes except (the first?/lowest?) 10 into HMA don't know if this is possible. Bart is the expert here. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] root entries field
On Tue, 23 Mar 2004, Arkady V.Belousov wrote: Bart, let me remind me %subject% issue: why FD returns nonzero field for FAT32 in (and only in) current BPB? most likely because of dsk.c: pbpbarray-bpb_ndirent = 512; Why that line is there? I don't know. It was already in the first FAT32 kernel from Victor Vlasenko so he's the one who put it in. I think this line can be removed. For the default bpb it's correctly set to 0 in initdisk.c Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: [Freedos-cvs] kernel/kernel fatdir.c,1.40,1.41 etc
Hi! 22--2004 14:47 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to FreeDOS-kernel [EMAIL PROTECTED]: if (new_diroff == 65535) Borland C++ complains here. Change the constant to 65535UL (see patch below). Hm, don't see letter with these words. LG Although Borland says constant is long, it's enough to change it to LG 65535U, not UL. Or 0x - as rightly noted by Bart, numeric literals with 0x prefix default are unsigned. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: kernel/kernel fatfs.c,1.52,1.53 proto.h,1.50,1.51 memmgr.c,1.27,1.28
On Mon, 22 Mar 2004, Eric Auer wrote: Hi, about add_far() pointer normalization: I think it would be better to normalize earlier. If you have a pointer, you normally have a pointer to a STRUCTURE. If the end of the structure ends up with an offset 0x then having the POINTER normalized is not enough. So how do you check the SIZE of the structure for which you normalize the pointer? Or do you just have an hardcoded constant maximum structure size for structures for which the add_far function can be used? add_far is only used at a few select places where we want to have the offset part as low as possible. Nothing to do with structures but everything to do with potentially large file reads, with read chunk, update pointer loops. Quite possibly Arkady's approach minimizing normalizations has merit but then each add_far caller needs to be checked if it needs to manually normalize the pointer afterwards. But for now, because it's not called very often, the time it takes is very small in comparison with the BIOS calls following, and normalization doesn't hurt, I haven't changed it. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: Last change introduced an unknown unit delete bug
On Mon, 22 Mar 2004, Luchezar Georgiev wrote: :\elv_3e5.1 I mean i:\elv_3e5.1 Sorry for my typo! should be fixed now. remove_lfn_entries() calls dir_read with the offset == -1 which is not possible for normal directories (. and ..) but is possible for root directories. So the 65535 check only needs to be applied to non-root directories; the real limit for root directories is checked somewhere further down the line. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: kernel/kernel fatfs.c,1.52,1.53 proto.h,1.50,1.51 memmgr.c,1.27,1.28
Hi!
22--2004 14:23 [EMAIL PROTECTED] (Bart Oldeman) wrote to
[EMAIL PROTECTED]:
BO add_far is only used at a few select places where we want to have the
BO offset part as low as possible. Nothing to do with structures but
BO everything to do with potentially large file reads, with read chunk,
BO update pointer loops.
BO Quite possibly Arkady's approach minimizing normalizations has merit but
BO then each add_far caller needs to be checked if it needs to manually
BO normalize the pointer afterwards.
Then rename add_far into normalize_ptr and remove misleading. Also,
I may offer next code to always perform normalization: (BTW, is protection
from wrapping HMA pointer into IVT by replacing wrapping into start of HMA
worth of code?)
void FAR *normalize_ptr (void FAR *fp, unsigned add)
{
unsigned ofs = add + FP_OFF (fp);
seg/*_t*/ s = FP_SEG (fp);
if (ofs FP_OFF (fp))/* arithmetic overflow? */
s += 0x1000;/* add carry */
return MK_FP ((ofs 4) + s, 0xF ofs);
}
BO But for now, because it's not called very often, the time it takes is very
BO small in comparison with the BIOS calls following, and normalization doesn't
BO hurt, I haven't changed it.
---
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
___
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Last change introduced an unknown unit delete bug
Bart, unfortunately your very last change (scaling and shortening the directory entry pointer) introduced a bug! When I start my elvis editor (a vi clone) and exit it, it can't delete its temporary file ELV_3E5.1 from my XMSDSK RAM disk where is my temporary directory. 4DOS fails to delete it saying 4DOS: (Sys) Bad disk unit :\elv_3e5.1. When I test this with rm in STEPDOS I see that the UNLINK (delete file) DOS function (41h) fails with return code of 14h (unknown unit) which isn't even allowed for it and is an Int 24h error! What's going on here? A slight detailisation. This error is returned on attempt to rename the file or delete it. But all reads on it succeed. So, it must be happening only on directory writes. Besides, I may be wrong that this bug was introduced by your very last changes, because I haven't checked the contents of my drive I: for a while (probably a couple of days). So it may be a result of a slightly earlier change, but in all cases it's a very recent change. Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: kernel/kernel fatfs.c,1.52,1.53 proto.h,1.50,1.51 memmgr.c,1.27,1.28
Hello Arkady, AVB Then rename add_far into normalize_ptr and remove misleading. noone is going to rename functions because you don't like the names. AVB Also, AVB I may offer next code to always perform normalization: It's there for some specific purpose. AVB (BTW, is protection AVB from wrapping HMA pointer into IVT by replacing wrapping into start of HMA AVB worth of code?) a working kernel is worth a lot of code (even if you don't see the reason immediately) HANDS OFF THE KERNEL, please. tom --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: Last change introduced an unknown unit bug
On Mon, 22 Mar 2004, Luchezar Georgiev wrote: But what if it was the first entry in the root directory? Then the new_diroff++ in dir_read() will make it -1! remove_lfn_entries() checks for fnp-f_diroff == 0. The first entry can't have any LFN entries connected to it. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] LF written to the file being read?
But what if it was the first entry in the root directory? Then the new_diroff++ in dir_read() will make it -1! remove_lfn_entries() checks for fnp-f_diroff == 0. The first entry can't have any LFN entries connected to it. Of course! I should have seen that. This is so for lfn_dir_read() too. I wanted to ask you one more question: chario.c:read_line_handle() calls echo_char(LF, sft_idx) - doesn't this write the LF to the file being read? Thanks for the 240 more low memory bytes, by the way! ;-) Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: kernel/kernel fatfs.c,1.52,1.53 proto.h,1.50,1.51 memmgr.c,1.27,1.28
On Mon, 22 Mar 2004, tom ehlert wrote: AVB (BTW, is protection AVB from wrapping HMA pointer into IVT by replacing wrapping into start of HMA AVB worth of code?) a working kernel is worth a lot of code (even if you don't see the reason immediately) HANDS OFF THE KERNEL, please. in the end it was just easier to remove add_far() and use buffer = adjust_far(buffer + offset). The only users are dsk.c and fatfs.c, where this is safe as long as you normalize the pointer before the loop. Which it was in fatfs.c but not in dsk.c. For the HMA. Yes, hands off: we do often read things (indirectly) into the HMA, there are BUFFERs there for instance. Maybe, just maybe, we're safe now with removing HMA logic from adjust_far() -- but it's way too easy to break this and will lead to bugs that are hard to solve. The current CVS kernel now has a 450 bytes smaller HMA_TEXT than ke2033 :) Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Extra CRs after input in output file
On Thu, 18 Mar 2004 11:14:39 +0200, I wrote: the redirected output contains two consequtive carriage returns though. I mean that the output file contains extra CRs only after the r and q input commands, not where DEBUG does its own output. Good news - I now saw that this is exactly the same under MS-DOS 7.1! So let it be this way ;-) Lucho http://linux.tu-varna.acad.bg/~lig/freedos/CVSPATCH.TXT http://linux.tu-varna.acad.bg/~lig/romdsk/romd-bin.rar --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: editing command line
Hi! 21--2004 17:06 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to [EMAIL PROTECTED]: I use both features (F3 and Ins to edit command line) in MS-DOS often. BTW, they are also available in DEBUG. Isn't this mean, that editing features built-in into kernel? LG Yes. They're implemented in chario.c:read_line() and are available even LG after shell EXIT when you type another shell name ;-) I mean: is this mean, that editing code is/should duplicated in kernel and command.com? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: editing command line
I mean: is this mean, that editing code is/should duplicated in kernel and command.com? As far as I know, no. FreeCOM has its own command line editor with history and auto-competion. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: editing command line
AVB 1. In kernel present editing code. yes. AVB 2. If code presented in command.com, how this affects other programs (say, AVBDEBUG)? command.com implements it's own doswedit-style input editor. it doesn't affect other programs (it's not exported) tom --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: editing command line
I mean: is this mean, that editing code is/should duplicated in kernel and command.com? As far as I know, no. FreeCOM has its own command line editor with history and auto-completion. But: 1. In kernel present editing code. 2. If code presented in command.com, how this affects other programs (say, DEBUG)? I already wrote that it's in the kernel, not in the shell. Any function 0Ah (3Fh) call does it. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: editing command line
Hi! 21--2004 19:50 [EMAIL PROTECTED] (tom ehlert) wrote to Arkady V.Belousov [EMAIL PROTECTED]: I again send not finished sentence. :( I mean: AVB 1. In kernel present editing code. te yes. ...then which reason to reimplement this in command.com? AVB 2. If code presented in command.com, how this affects other programs (say, AVBDEBUG)? te command.com implements it's own doswedit-style input editor. te it doesn't affect other programs (it's not exported) ...then which reason to reimplement this in command.com? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Re: editing command line
The F3-style command line editing is in the kernel because function 0Ah (3Fh when reading from standard input) in MS-DOS does it. Period. As to FreeCOM, it has a better (4DOS-style) command line editing and I don't see a reason for a separate DOSEDIT. Period. I'll not answer anymore. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] chario.c, dsk.c, floppy.asm patches
On Sun, 21 Mar 2004 23:42:26 + (GMT), Bart Oldeman wrote: It appears that ^C has to be echoed to stdout. This is easy to test, I'm using a simple test0a program, see below. If you (in MSDOS) run test0a foo and press ^C then the ^C ends up in foo. Or if I run DEBUG BOZA then type ^C and Q then BOZA contains the ^C, so you're right indeed! Boza (millet-ale) is a very specific thick light-brown Bulgarian drink that I don't like and is our rough equivalent to FOO.BAR (there is also a virus with this name, Bulgarian, of course ;-) Which is not stderr. I thought that stderr is more logical, but as I see, Microsoft didn't think so :( Let it be! :) Also about LF. Press ctrl-j and you'll see it is echo'ed as cr-lf, except when you're still at the beginning of a line and it's the first key you press. ctrl-j ctrl-j or ctrl-f ctrl-j already does the trick. Most likely the first time trick is to deal with cr-lf from redirected input, indeed. OK. Most important is that your changes fix the DEBUG redirectioj bug, too! So I accept them. I'm leaving your floppy changes out of the kernel for the time being as you are still dry swimming as far as I understood, and RBIL specifically says about int13/ah=16 B-1316--- INT 13 - FLOPPY DISK - DETECT DISK CHANGE (XT 1986/1/10 or later,XT286,AT,PS) AH = 16h DL = drive number (00h-7Fh) that the TSR lets this function be valid for DL=80 I still find hard to believe Wow! I didn't notice that this call is only for floppy disks (0-7F)! So you're right again, as usual! ;-) Well, Bart, congratulations and thanks for your changes that fix those bugs! As to my dry swimming, it's because I don't have a ZIP drive [yet] to test its disk change... So, this bug will have to wait until I buy one just to see what's going on :-( Don't you just hate IOMEGA? ;-G Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] nevermind..
reason is speedup. It's faster to read a single 360KB file into RAM and then run from there, than to keep reading a diskette. guess you had the bootdisk from prerelease 4, or the one below: http://fdos.org/ripcord/beta9rc5/fdos1440.img the real floppy contents is accessible as B: are you the same Wørm who had a bootdisk site? it disappeared quite a while ago. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] freedos boot problems / about me
it's the CDRcache driver which causes the cdrom disk resets, not SHSUCDX itself. option 2 should prevent it from loading, as no XMS driver is loaded. Bernd --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] redirection BUG
That's strange. Then MS-DOS DEBUG would also leak handles... the difference is that msdos debug calls int21/ah=26 instead of 55. Here's a kernel bug inspired by the RBIL comment this function is implemented using the same code as AH=26h taken too literally... Reality is that the only things that ah=26h should do is to copy the PSP (from CS, not the cu_psp value) set int22,23,24 and set parent PSP to 0. ah=55 does a lot more. Well this will take a little longer to fix so I'll do that later. It does mean however that FD debug will need to call ah=26 and not ah=55 to avoid leaking handles. Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] DEBUG redirection bug fixed, 2 new remain
On Wed, 17 Mar 2004 13:37:07 + (GMT), Bart Oldeman wrote: It looks like a bug in both DEBUG and the kernel. What happens is the reference count in the SFT gets too high. 1. open: 1 2. int21/ax=4b: 2 3. int21/ax=55: 3 (this function called by debug) then: 4. int20: 2 5. int21/ah= 3e: 1 ... and the file still isn't really closed If you do the redirection again then it will use new sft entries. Just do the above a couple of times and you'll see that opening a file gives an sft idx entry in the PSP that is higher and higher... in other words, leaked file handles... Wow! What a nightmare! :-( It doesn't hurt to commit (sync) the file though so with the patch below the problem is solved. And this is so for both MS-DOS DEBUG and FreeDOS DEBUG, as it seems from your and my tests... That's strange. Then MS-DOS DEBUG would also leak handles... Seems so, because applying your patch FIXED the problem with MS-DEBUG too! Congratulations! :-) So far so good. But when the input debug SCRIPT contains just these lines: r q doing DEBUG SCRIPT starts to output NULs and BEEPs! Pressing Ctrl-C stops it, but then the SCRIPT file has that ^C appended! This is like a similar bug we had - do you remember? :-( But when SCRIPT has only CARRIAGE RETURNs as line terminators (without line feeds), it's OK! So we have yet another TWO bugs to fix :-( Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Patch: ZIP media change not detected bug fix
On Wed, 17 Mar 2004, Luchezar Georgiev wrote: The patch below should fix the ZIP media change not detected bug, *if* my assumption about ZIP driver setting both DF_FIXED and DF_CHANGELINE is right. Never hurts to assume that this MAY happen though... If the ZIP drive has its own device driver (with DEVICE=) than whatever is in floppy.asm has no influence. Or is it really handled via the BIOS as drive A: or drive C:? In any case a change to init_readdasd in initdisk.c (+ your change in dsk.c) may be more appropriate than floppy.asm since the changeline status of a drive won't change after booting -- and I don't think DOS is advanced enough to handle hotplugging between non-changeline and changeline floppy drives... Bart --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Patch: ZIP media change not detected bug fix
Bart, Or is it really handled via the BIOS as drive A: or drive C:? My PC allows for ZIP to be set as first boot device. IF a disk is in it during bootup it is seen as C: -or- If I use Iomega's DOS level drivers GUEST.EXE program on a bootable floppy disk in A: AND a disk is in the ZIP drive, then my ZIP drive gets assigned C: -or- If NO disk is in ZIP drive, then it's NOT seen nor recognized by anything. -Or- If no disk but Iomega DOS level drivers GUEST.EXE loaded, then any disk ZIP disk gets assigned D: This is an EIDE ZIP 100 drive, NOT a SCSI or other type, on ATA2 as slave.fwiw. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] redirection BUG
On Mon, 15 Mar 2004 22:27:45 +0300 (MSK), Arkady V.Belousov wrote: a int 3 g=100 q Run DEBUGT.DRESULT (where DEBUG is by Paul Vojta, MS-DEBUG doesn't work under FreeDOS). This is wrong. MS-DOS 7.10 DEBUG *does* work under FreeDOS 7.10! I've used it many many times. Under MS-DOS result file is fine, under FreeDOS redirected file is zero size. Noted by Bernd Blaauw I don't understand anything. What redirected file? The above script just sets a break-point. Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Arkady, Jim, please, retest with latest bootfix version (1.3) - now it analyzes not only default, but also current BPB. Zip file sent to you. beta9rc4 is outdated and definitely should be updated. Considering comments by Luchezar G, there's something wrong on the server I got that ISO image off of. Perhaps it's dishing out old cached copies of 2.9 not current build. This (error in creating C:\KERNEL.SYS by SYS) is, probably, result of running SYS under older kernel? I think, if you now boot under newer kernel, then this error will disappear. THAT particular error WAS under newest build 2033_32. I got it after booting off of such a floppy disk created by that build. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] redirection BUG
Hi! 16--2004 18:32 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to [EMAIL PROTECTED]: LG So, when I have time (at the week end probably), I'll try to catch the LG bug. If Bart has time, he may want to overtake me ;-) Probably, this is not the last bug. I wait details from Jim Lilly, but looks like FreeDOS doesn't sense media change (in Zip drive, available as C:), and uses old BPB for new media. As result, we have FAT32 (current) BPB for FAT16 boot record. Also, by some (unknown for me) reason in current BPB for FAT32 not zeroed rootEntries field (whereas it clear in default BPB and boot record). I ask Jim to perform test: scan FAT32, then FAT16 diskettes, then reboot, then perform scan in reverse order. Will see the results. PS: 32-bit enabled kernel completely successfuly (no errors, no warnings) shows my FAT16 and FAT12 media. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] ZIP media change not sensed bug
On Tue, 16 Mar 2004 22:01:22 +0300 (MSK), Arkady V.Belousov wrote: Probably, this is not the last bug. Last bug?! You know just like every order in the army, every bug is a last but one ;) looks like FreeDOS doesn't sense media change (in Zip drive, available as C:) This is probably because dsk.c:diskchange() returns M_NOT_CHANGED if hd(pddt-ddt_descflags). Perhaps the ZIP driver sets both FD_FIXED and DF_CHANGELINE flags. If so, this can easily be fixed, but I'd also add an Int 13h AH=15h (disk changeline support) check before calling Int 13h AH=16h (read change status) in drivers/floppy.asm:_fl_diskchanged(). But all the above are just hypotheses. If someone donates me a ZIP drive, I could test all this and fix the bug ;-) Otherwise it's a big pain for both parties when a beta-tester has to test and test and test endlessly... until just before the fix, he gives up :( Had happened not once! Or perhaps I should buy a ZIP drive just to be able to fix that bug?! ;) Unfortunately, we're not Microsoft! :( Fortunately, we're not Micro$oft! :) Lucho P.S. Now when I cried enough, I think that after fixing the DEBUG redirection bug, I can patch diskchange() and fl_diskchange() and ask Jim to try. But the DEBUG redirection bug worries me! --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
On Mon, 15 Mar 2004 13:45:43 +0300 (MSK), Arkady V.Belousov wrote: So, there was a bug in kernel, which was used previously. This should be reported for those, who prepare ISO images: beta9rc4 is outdated and definitely should be updated. There is something wrong here. The latest official kernel (build 2033) went out on 31 January. Pre-release 4 distribution went out 5 days later, on 5 February. So it did include kernel 2033! Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 15--2004 12:23 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to [EMAIL PROTECTED]: should be reported for those, who prepare ISO images: beta9rc4 is outdated and definitely should be updated. LG There is something wrong here. The latest official kernel (build 2033) LG went out on 31 January. Pre-release 4 distribution went out 5 days later, LG on 5 February. So it did include kernel 2033! I only try to remind words of Jim Lilly, which has troubles with this edition - and he report, that there was SYS 2.9. After updating kernel (and SYS) to 2033 FAT32 Zip diskette was handled correctly. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot code testing???
On Sat, 13 Mar 2004 19:16:00 CST, Jim Lilly wrote: If I remember correctly, FAT32 volumes must be at least 128 MB in size. Where might I read up on that info? Microsoft have stated that the minimum is even 256 MB (in http://www.microsoft.com/windows98/usingwindows/maintaining/articles/901Jan/Fat32.asp) but I remember that someone was trying to boot FreeDOS off a 64 MB FAT32 partition, which didn't work, but when he switched to a 128 MB partition, it worked. Unfortunately, I'm not good at searching old messages, so I was unable to find the exact message, and even don't know in which mailing list it was - sorry! In any case, ZIP disks must be formatted with FAT16 and nothing else. Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot code testing???
Luchezar, In any case, ZIP disks must be formatted with FAT16 and nothing else. Yep, just had the link to Iomega stating that sent to me. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot code testing???
Hi! 12--2004 21:08 [EMAIL PROTECTED] (Jim Lilly) wrote to [EMAIL PROTECTED], Arkady V.Belousov: JL I tried the only updating the boot sector using FreeDOS' SYS and got; JL D:\Download\FreeDOSsys X: BOOTONLY JL FreeDOS System Installer v2.9, Sep 24 2003 JL Processing boot sector... JL Reading old bootsector from drive X: JL Divide overflow JL WinXP throws up an error message because I'm trying to directly access JL hardware, but I'm allowed to ignore proceed. - v2.9 is outdated (old kernel). - in SYS (also as in my BOOTFIX, which' IO based on code from SYS) is a bug (when calling INT 21/7305, CF is not set nor checked if after interrupt AX=7300, thus under NT/2k/XP processed wrong data), which doesn't allow to say about error reading (old) boot sector. - you can't use SYS (and any other programs, which directly access disks) under NT/2k/XP. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot code testing???
Hi! 12--2004 20:02 [EMAIL PROTECTED] (Jim Lilly) wrote to [EMAIL PROTECTED], Arkady V.Belousov: This is FAT16, so FAT size here should be 190 sectors. JL Hmmm, THAT particular disk should have been FAT32or I got confused. This disk (with such clusters count) can't be FAT32. Under which OS you run BOOTFIX? JL WinXP Pro, and it's HD is NTFSfwiw. No, NT-family doesn't allows to directly access (read) disks and, probably, there may be returned wrong data for BPB. So, to use any disk accessing DOS programs, you should do this under DOS (or, W9x). --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 13--2004 15:44 [EMAIL PROTECTED] (Jim Lilly) wrote to ark: JL Attached is [misc.zip] JL File notes from Jim Lilly; JL RSLT_SR6 - ZIP100, FAT, BOOTFIX results Looks valid and workable. JL RSLT_16 - ZIP100, FAT, BOOTFIX results Looks like there is problems: OS says that FAT starts from sector 1, whereas boot record says that FAT starts from sector 8. This may cause data corruption if you will write into this drive. Which OS you was use for tests? Which software you use to prepare (format) these ZIP diskettes? Also, disk geometry in boot record differs from one, reported by OS. This is, probably, not very important (in given case), but who knows. Also, as sayed by volume label, first disk (which is consistent) is from SPINRITE package (or formated by SPINRITE :). JL RSLT_32 - ZIP100, FAT32, BOOTFIX results Completely incorrect results: boot records says, that this is FAT32, whereas OS says, that this is FAT16. Any file write should be dangerous. Looks like this diskette was prepared by NT-family (XP?) - boot sector mentions NTLDR. JL Bootsect32.BMP - ZIP100, FAT32, on screen error message, COPYBS C: JL bootsect Let me quote: __O\_/_\_/O__ [...] A:copybs C: btsec_16 A:copybs C: btsec_32 ERROR: Filesystem not found on disk _ O/~\ /~\O Error message looks valid. JL OddErrors.BMP - on screen goofy errors after I got (bootsect32.bmp) JL error. __O\_/_\_/O__ String #127 String #127 String #127 String #127 String #127 String #127 String #120 String #121 String #123 String #124 A:\dir /w /p |MORE String #16 A:\C: A:\dir /w /p String #116 String #118 String #119 String #12 C:\ _ O/~\ /~\O If you test this under FreeDOS, you should report this to Steffen Kaiser, author of command.com. JL All tests done from bootup floppy disk, on ZIP100 seen as drive C: JL Unable to get BOOTSECT (COPYBS) for ZIP100 as FAT32, see Bootsect.bmp. This is because file system here is incorrectly detected by OS. JL PC system info; JL Maxtor 80GB HDD on IDE3 (hpt370) NTFS, 3 partitions. JL ZIP100 on IDE2 as slave (which is why the ZIP100 gets seen as C: in JL tests) --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot code testing???
Arkady, http://makeashorterlink.com/?K379136B7 Should I format my Jaz or Zip disk with FAT32? Answer Iomega® does not support nor recommend the use of FAT32 formatting with Zip® or Jaz® disks. Warning: Data integrity maybe an issue using FAT32 formatting. Iomega recommends formatting Zip and Jaz disks with the IomegaWare software format option. WinXP wrongly allows me to format a ZIP-100 disk as FAT32, which ends up NOT bootable. Iomega ONLY recommends FAT NOT FAT32 for ZIP/JAZZ disks. My conclusion then, is this; 1) MS's suggested minimum FAT32 partition size is 512MB 2) As a true HD, mathematically, 33MB is minimum for FAT32 partitions. 3) As a removable drive (ZIP/JAZZ) Iomega recommends ONLY FAT NOT FAT 32for such disks. Only issue I'd wonder about, is why does FreeDOS claims to have succeeded in formatting a ZIP 100 disk (formatted as FAT32) when in actual use such a disk fails to be bootable? I'll test that some more, today if I get a chance. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 14--2004 14:33 Arkady V.Belousov wrote to [EMAIL PROTECTED]: JL Attached is [misc.zip] JL File notes from Jim Lilly; JL RSLT_SR6 - ZIP100, FAT, BOOTFIX results __O\_/_\_/O__ Checking drive C: Reading default BPB... [...] Volume is a FAT16. Reading boot sector... Bytes/sector : 512 Sectors/cluster : 4 FAT start, size : 1, 192 * 2 Root entries : 512 Total sectors : 0, 196576 Hidden sectors: 32 Sectors/track, heads : 32, 64 Drive, media ID, FS : 80h, F8h, FAT16 Serial#, label: h, SPINRITE V6 Done. Boot sector: EB 40 90 46 72 65 65 44-4F 53 20 00 02 04 01 00 [EMAIL PROTECTED] . 0010 02 00 02 00 00 F8 C0 00-20 00 40 00 20 00 00 00 .. [EMAIL PROTECTED] ... 0020 E0 FF 02 00 80 00 29 00-00 00 00 53 50 49 4E 52 ...)SPINR 0030 49 54 45 20 56 36 46 41-54 31 36 20 20 20 00 00 ITE V6FAT16 .. [...] 01F0 00 4B 45 52 4E 45 4C 20-20 53 59 53 00 00 55 AA .KERNEL SYS..U _ O/~\ /~\O Default BPB is equal to boot record. JL RSLT_16 - ZIP100, FAT, BOOTFIX results __O\_/_\_/O__ Reading default BPB... Bytes/sector : 512 Sectors/cluster : 4 FAT start, size : 1, 192 * 2 Root entries : 512 Total sectors : 0, 196576 Hidden sectors: 32 Sectors/track, heads : 32, 64 Media ID : F8h Done. Volume is a FAT16. Reading boot sector... Bytes/sector : 512 Sectors/cluster : 4 FAT start, size : 8, 192 * 2 Root entries : 512 Total sectors : 0, 196576 Hidden sectors: 32 Sectors/track, heads : 63, 255 Drive, media ID, FS : 80h, F8h, FAT16 Serial#, label: 335D1509h, NO NAME Done. Boot sector: EB 3C 90 4D 53 57 49 4E-34 2E 31 00 02 04 08 00 MSWIN4.1. 0010 02 00 02 00 00 F8 C0 00-3F 00 FF 00 20 00 00 00 ..?.. ... 0020 E0 FF 02 00 80 00 29 09-15 5D 33 4E 4F 20 4E 41 ...)..]3NO NA 0030 4D 45 20 20 20 20 46 41-54 31 36 20 20 20 33 C9 MEFAT16 3 [...] 01D0 20 6B 65 79 0D 0A 00 00-49 4F 20 20 20 20 20 20 keyIO 01E0 53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7F 01 SYSMSDOS SYS. 01F0 00 41 BB 00 07 60 66 6A-00 E9 3B FF 00 00 55 AA .A..`fj.;..U _ O/~\ /~\O JL RSLT_32 - ZIP100, FAT32, BOOTFIX results __O\_/_\_/O__ Reading default BPB... Bytes/sector : 512 Sectors/cluster : 4 FAT start, size : 1, 192 * 2 Root entries : 512 Total sectors : 0, 196576 Hidden sectors: 32 Sectors/track, heads : 32, 64 Media ID : F8h Done. Volume is a FAT16. Reading boot sector... Bytes/sector : 512 Sectors/cluster : 2 FAT start, size : 36, 762 * 2 Root cluster : 2 Total sectors : 0, 196576 Hidden sectors: 32 Sectors/track, heads : 63, 255 Version, mirror flags : h, 00h Info, backup sectors : 1, 6 Drive, media ID, FS : 00h, F8h, FAT32 Serial#, label: C8EAFE6Ch, NO NAME Done. ERROR: boot record differs from defaults. Boot sector: EB 58 90 4D 53 44 4F 53-35 2E 30 00 02 02 24 00 XMSDOS5.0...$. 0010 02 00 00 00 00 F8 00 00-3F 00 FF 00 20 00 00 00 ...?.. ... 0020 E0 FF 02 00 FA 02 00 00-00 00 00 00 02 00 00 00 . 0030 01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00 0040 00 00 29 6C FE EA C8 4E-4F 20 4E 41 4D 45 20 20 ..)lNO NAME 0050 20 20 46 41 54 33 32 20-20 20 33 C9 8E D1 BC F4FAT32 3 [...] 0170 4E 54 4C 44 52 20 20 20-20 20 20 00 00 00 00 00 NTLDR . 0180 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 0190 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 01A0 00 00 00 00 00 00 00 00-00 00 00 00 0D 0A 52 65 ..Re 01B0 6D 6F 76 65 20 64 69 73-6B 73 20 6F 72 20 6F 74 move disks or ot 01C0 68 65 72 20 6D 65 64 69-61 2E FF 0D 0A 44 69 73 her media...Dis 01D0 6B 20 65 72 72 6F 72 FF-0D 0A 50 72 65 73 73 20 k error..Press 01E0 61 6E 79 20 6B 65 79 20-74 6F 20 72 65 73 74 61 any key to resta 01F0 72 74 0D 0A 00 00 00 00-00 AC CB D8 00 00 55 AA rt.U _ O/~\ /~\O --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Arkady, Which OS you was use for tests? FreeDOS Which software you use to prepare (format) these ZIP diskettes? WinXP Pro initially, SpinRite for the one ZIP disk. Also, disk geometry in boot record differs from one, reported by OS. This is, probably, not very important (in given case), but who knows. Also, as sayed by volume label, first disk (which is consistent) is from SPINRITE package (or formated by SPINRITE :). SpinRite uses FreeDOS. Completely incorrect results: boot records says, that this is FAT32, whereas OS says, that this is FAT16. Any file write should be dangerous. Looks like this diskette was prepared by NT-family (XP?) - boot sector mentions NTLDR. Correct. WinXP Pro (incorrectly) allows me to set format of ZIP-100 disks to FAT32, which ends up non-bootable. SpinRite which uses FreeDOS incorrectly 'claims' to have successfully formatted such FAT32 ZIP-100 disks.yet fail to boot. THAT is the focal point of troubles with FreeDOS I'm having. SpinRite uses FreeDOS for it's formatting functions. Under WinXP Pro, a ZIP- 100 (incorrectly) formatted as FAT32 is NOT getting correctly formatted. Shouldn't it (SR/FreeDOS) give an error message about incorrect file format/ bad bootsector? It does IF the ZIP-100 is formatted as NTFS. JL OddErrors.BMP - on screen goofy errors after I got (bootsect32.bmp) JL error. If you test this under FreeDOS, you should report this to Steffen Kaiser, author of command.com. What's his e-mail address? -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot code testing???
Arkady, - v2.9 is outdated (old kernel). Might be, but it's what's on. http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/beta 9rc4/fdbootcd.zip Also note; THAT CD of FreeDOS did NOT 'see' anything but the CDROM Floppy drivesno ZIP, no HD. - You can't use SYS (and any other programs, which directly access disks) under NT/2k/XP. HDD's, true. But as I stated earlier, WinXP throws up an error message because I'm trying to directly access hardware, but I'm allowed to ignore proceed. Probably because that ZIP drive is recognized as a 'removable disk' and not a true HD. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
On Sun, 14 Mar 2004 07:55:10 CST, Jim Lilly wrote: [...] SpinRite which uses FreeDOS incorrectly 'claims' to have successfully formatted such FAT32 ZIP-100 disks.yet fail to boot. THAT is the focal point of troubles with FreeDOS I'm having. SpinRite uses FreeDOS for it's formatting functions. Under WinXP Pro, a ZIP-100 (incorrectly) formatted as FAT32 is NOT getting correctly formatted. Shouldn't it (SR/FreeDOS) give an error message about incorrect file format/ bad bootsector? It does IF the ZIP-100 is formatted as NTFS. The SpinRate author Steve Gibson participates here, but the official FreeDOS formatting tool is FORMAT currently maintained by Eric Auer. Why don't you try to use FORMAT on your ZIP first? By the way, doesn't IOMEGA recommend that only their tools be used for formatting ZIP disks? Iomega recommends formatting Zip and Jaz disks with the IomegaWare software format option. Perhaps ZIPs are somewhat non-standard and / or picky about the tools used to deal with them? Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Luchezar, FreeDOS formatting tool is FORMAT currently maintained by Eric Auer. Why don't you try to use FORMAT on your ZIP first? I would if I could, but FreeDOS doesn't 'see' the ZIP drive, it only sees A: the CDROM. Therefore FreeDOS won't allow me to do anything to my ZIP drive. By the way, doesn't IOMEGA recommend that only their tools be used for formatting ZIP disks? Correct, which I only found out about this morning. Perhaps ZIPs are somewhat non-standard and / or picky about the tools used to deal with them? Perhaps you missed this; http://makeashorterlink.com/?K379136B7 Should I format my Jaz or Zip disk with FAT32? Answer Iomega® does not support nor recommend the use of FAT32 formatting with Zip® or Jaz® disks. Warning: Data integrity maybe an issue using FAT32 formatting. Iomega recommends formatting Zip and Jaz disks with the IomegaWare software format option. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
On Sun, 14 Mar 2004 08:32:47 CST, Jim Lilly wrote: FreeDOS formatting tool is FORMAT currently maintained by Eric Auer. Why don't you try to use FORMAT on your ZIP first? I would if I could, but FreeDOS doesn't 'see' the ZIP drive, it only sees A: the CDROM. Therefore FreeDOS won't allow me to do anything to my ZIP drive. FreeDOS has no built-in ZIP support. Don't IOMEGA offer a DOS driver for their ZIP drives? Have you tried such a driver in MS-DOS or FreeDOS? Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Luchezar, Have you tried such a driver in MS-DOS or FreeDOS? I'll setup a DOS bootdisk as such. How is such done with a FreeDOS boot floppy? -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
On Sun, 14 Mar 2004 10:15:30 CST, Jim Lilly wrote: Luchezar, No need to send me a carbon copy, I'm subscribed here. Have you tried such a driver in MS-DOS or FreeDOS? I'll setup a DOS bootdisk as such. How is such done with a FreeDOS boot floppy? ODIN is already bootable (see FreeDOS site for its URL) You need to make a CONFIG.SYS (device=iomega_driver_name) If this turns into an user issue, ask FreeDOS-user list. (Do you mean that IOMEGA still really support DOS??? ;-) Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 14--2004 07:55 [EMAIL PROTECTED] (Jim Lilly) wrote to [EMAIL PROTECTED], Arkady V.Belousov: Not needed to CC for me, I subscribed to [EMAIL PROTECTED] Which OS you was use for tests? JL FreeDOS Probably, bug in FreeDOS kernel. I think, Bart may/should clarify this, may this is expected behavior. Completely incorrect results: boot records says, that this is FAT32, whereas OS says, that this is FAT16. Any file write should be dangerous. Looks like this diskette was prepared by NT-family (XP?) - boot sector mentions NTLDR. JL Correct. WinXP Pro (incorrectly) allows me to set format of ZIP-100 disks to JL FAT32, I don't sure that this is incorrect - URL, which gives Luchezar, doesn't says why FAT32 volumes _must_ be 128 Mb, there is only recomendation. Moreover, if MS-FORMAT allows to format 100 Mb as FAT32 (and XP works with it flawlessly?), then this should be accepted by us also. JL which ends up non-bootable. Do you mean, that - XP formats to FAT16 and makes bootable: diskette boots - XP formats to FAT32 and makes bootable: diskette bot boots ? JL SpinRite which uses FreeDOS incorrectly 'claims' to have successfully JL formatted such FAT32 ZIP-100 disks.yet fail to boot. This is question for Steve, author of SpinRite. JL THAT is the focal point of troubles with FreeDOS I'm having. JL SpinRite uses FreeDOS for it's formatting functions. No, DOS doesn't used for formatting functions, DOS is only host OS (for program) and it may present file system information for application. JL Under WinXP Pro, a ZIP-100 (incorrectly) formatted as FAT32 is NOT getting JL correctly formatted. Shouldn't it (SR/FreeDOS) give an error message about JL incorrect file format/bad bootsector? I think, it should use FAT32 as FAT32. If you test this under FreeDOS, you should report this to Steffen Kaiser, author of command.com. JL What's his e-mail address? 1. He subscribed to [EMAIL PROTECTED] 2. He subscribed here. 3. You may/should (also) use bugzilla to report error. I think, beforehand you should find ways how to reproduce the problem. Also, don't forget to download latest kernel and shell from freedos.sf.net. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Steve from GRC.COM said you needed testers
On Sun, 14 Mar 2004 17:42:11 -, James Stockton wrote: Tell me what to test smile And another! Not Iomega Zip/Jazz G FAT32 issues were mentioned. Please say required Kernel, etc. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 14--2004 20:47 Arkady V.Belousov wrote to [EMAIL PROTECTED]: AVB Probably, bug in FreeDOS kernel. I think, Bart may/should clarify AVB this, may this is expected behavior. ---^^^ may be AVB Do you mean, that AVB - XP formats to FAT16 and makes bootable: diskette boots AVB - XP formats to FAT32 and makes bootable: diskette bot boots ^^^ not --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] Steve from GRC.COM said you needed testers
Whats me choice of kernels smile? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
On Sun, 14 Mar 2004 20:47:44 +0300 (MSK), Arkady V.Belousov wrote: Which OS you was use for tests? FreeDOS Probably, bug in FreeDOS kernel. I think, Bart may/should clarify this, maybe this is expected behavior. What we're talking about here? Does the bootstrap from FreeDOS fail? If so, it's because of the bad boot sector. Does FORMAT under FreeDOS fail? No! Not only isn't FORMAT tested there yet, but he even has no driver for the ZIP drive installed (if any) yet! If so, how does SpinRite recognise the ZIP drive? Does it have its own driver for ZIP drives? I don't think so! Then?! Lucho --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 14--2004 20:47 Arkady V.Belousov wrote to [EMAIL PROTECTED]: AVB Probably, bug in FreeDOS kernel. Ops, sorry, too husty conlusion: BOOTFIX analyzes _default_ BPB, which is _suggestion_ by OS for given media. Boot record should be compared with current BPB, which is used by OS for control of media. Sorry for misleading you, late I prepare version, which will analyze current BPB (and compare it with boot record). About making FAT32 Zip diskette bootable: 1. get latest SYS version (comes with kernel, available at freedos.sf.net). 2. apply SYS to diskette (under latest kernel). 3. try to boot. Also, there are more issue: __O\_/_\_/O__ Reading default BPB... Hidden sectors: 32 Sectors/track, heads : 32, 64 Reading boot sector... Hidden sectors: 32 Sectors/track, heads : 63, 255 _ O/~\ /~\O There may be some issues with Hidden sectors field, which used by boot sector (installed by SYS) to find start of partition. Because Zip drive mapped as hard disk, then Zip diskettes should be partitioned. Run FreeFDISK and inform us about partition properties (address of start). Also, to format diskette, try to use FORMAT from Eric Auer. Eric, how to force FAT32 formatting in your FORMAT? --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Luchezar, You need to make a CONFIG.SYS (device=iomega_driver_name) Will do. (Do you mean that IOMEGA still really support DOS??? ;-) Nothing NEW, but older DOS/Win 3.1 drivers for 'guest' are available in their archives. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Luchezar, Does the bootstrap from FreeDOS fail? If so, it's because of the bad boot sector. Exactly! If so, it's because of the bad boot sector. Does FORMAT under FreeDOS fail? No! Undetermined, not No! But I'll check. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Arkady, Moreover, if MS-FORMAT allows to format 100 Mb as FAT32 (and XP works with it flawlessly?), then this should be accepted by us also. But it doesn't work 'flawlessly'. I can read/write/copy/move/delete to - from a ZIP-100 FAT32 disk, but it is NOT bootable. Do you mean, that - XP formats to FAT16 and makes bootable: diskette boots - XP formats to FAT32 and makes bootable: diskette bot boots ? No. - XP formats to FAT16 and can be made bootable: diskette boots - XP formats to FAT32: diskette is NOT bootable I'm using SR to transfer the FreeDOS boot info to the ZIP disks. No, DOS doesn't used for formatting functions, DOS is only host OS (for program) and it may present file system information for application. I* should correct that. In using SR to prep a ZIP-100 disk, it states; Retrieve previous boot sector from media Install FreeDOS boot sector onto media -then- A SpinRite bootable operating system has been successfully installed on drive X: It's not a FreeDOS formatting issue, but a FreeDOS boot-sector issue apparently. Like I said from the start, I'm NOT a programmer. Just a user am going to be busy this week with real life not have much more time to tinker with all of this. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 14--2004 08:32 [EMAIL PROTECTED] (Jim Lilly) wrote to [EMAIL PROTECTED], Luchezar Georgiev: FreeDOS formatting tool is FORMAT currently maintained by Eric Auer. Why don't you try to use FORMAT on your ZIP first? JL I would if I could, but FreeDOS doesn't 'see' the ZIP drive, it only sees A: But earlier you say, that you test BOOTFIX under FreeDOS and access Zip as C:? Also, note: diskettes and hard disks are handled differently - hard disk should be partitioned by FDISK(-like) program (and should contain MBR with partition table), diskettes always contain only one volume. So, if your Zip drive is mapped itself as hard disk, then Zip diskettes should be partitioned and formatted before usage. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Arkady, 1. get latest SYS version (comes with kernel, available at freedos.sf.net) Hmm, when I go to http://freedos.sourceforge.net/ I'm presented with a bunch of choices. Do you mean for me to get; kernel 2032? http://sourceforge.net/forum/forum.php?forum_id=312180 kernel 2033? http://prdownloads.sourceforge.net/freedos/ke2033_32.zip?download -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Arkady, But earlier you say, that you test BOOTFIX under FreeDOS and access Zip as C:? Probably when I'd used SR, booted off it, then switched diskettes. I'm beginning to get a bit overwhelmed with all of this. Maybe I'll tinker around some more tonight, before giving up. -- Jim Lilly - Team Z http://www.zonelabs.com/store/content/company/teamzBios.jsp Using - Virtual Access(OLR), ZAP 4.5, WinXP Pro w/SP1 http://www.virtual-access.org --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
I'm trying out the nightly kernel, not sure if thats what they mean. But its worth a look i think. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
On Sun, 14 Mar 2004 19:42:13 -, James Stockton wrote: I'm trying out the nightly kernel, not sure if thats what they mean. But its worth a look i think. As soon as I can get to it, will be using 2.0.33 http://prdownloads.sourceforge.net/freedos/ke2033_32.zip?download Trying to get the Net-bootable diskette image working at the moment --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Hi! 14--2004 13:32 [EMAIL PROTECTED] (Jim Lilly) wrote to [EMAIL PROTECTED]: 1. get latest SYS version (comes with kernel, available at freedos.sf.net) JL kernel 2033? Yes. Also, there was some changes in kernel. AFAIK, Luchezar presents precompiled kernels with all up to date patches (after latest official release) - look at his page. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70alloc_id638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
Re: [Freedos-kernel] FAT - FAT32 - SYS boot
Tested fat32 booting on me hard drive works fine. --- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470alloc_id=3638op=click ___ Freedos-kernel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-kernel
