Hi Michael, continuing the topic on freedos-kernel instead of freedos-user, maybe one of the kernel list readers has a precompiled kernel for you or can compile a kernel or several with debug options according to your choice enabled :-).
> For now, please link to the debug version! > Well, is there even some? Not precompiled, sorry. You can enable one or more of the following debug options in the config bat compile time options: DEBUG, DDEBUG, DEBUG_TRUENAME, DSK_DEBUG, NDEBUG, CHDIR_DEBUG, FIND_DEBUG and NLS_DEBUG Effects of those are, respectively: Debug info, let SYS dump the boot sector contents, verbose truename output (truename is called whenever you CHDIR or open a file or find a file using wildcards, also when you check file attributes, delete or rename a file, make or remove a directory, create a child env / start a program, and of course when apps call truename explicitly. In short you get insane amounts of debug info with DEBUG_TRUENAME). DSK_DEBUG shows very verbose info in getbpb (open drive) and when you transfer data from/to disk (block devices). Both NDEBUG and NLS_DEBUG are for NLS country settings but NDEBUG only enables log1() which is unused today?? NLS_DEBUG enables very verbose int 2f.14 debug output. Finally, CHDIR_DEBUG and FIND_DEBUG do exactly that: Let chdir and find (file with wildcards) output semi-verbose debug info. If you say you cannot load command.com but you have no config / autoexec, then DEBUG, DEBUG_TRUENAME(*), DSK_DEBUG(*), CHDIR_DEBUG and maybe FIND_DEBUG can be useful for you. But be aware that in particular those with (*) can be very verbose. You can put SCREEN=0x12 in config sys to switch to 50 line mode. If you enable DEBUG then dsk_init (InitDisk) will automatically use a switch to 50 line mode even without any config sys. > The bug is inside bootcode and/or kernel.sys before > it complains for missing command.com. Then a debug version of command.com will not help you, I guess... To check if the bug is in the bootcode, try installing something else than a kernel. For example you install METAKERN. Read the docs to know which SYS options you have to use for it. Note that metakern is small, so it is a bit easier to boot than kernel sys. > Error can be reproduced in VMware and in Bochs Can you put a (diskette?) image online so I can look at the error in Bochs myself as well? :-) Which disk and filesystem types are affected, e.g. LBA or CHS, floppy or harddisk, FAT12, FAT16 or FAT32...? Eric ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ Freedos-kernel mailing list Freedos-kernel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-kernel
