(I'm not sure I'm a member of the FreeDOS kernel mailinglist, can't find 
anything, so sticking to development list)

Right now when experimenting I'm experiencing an issue:
switching to B: by entering B: seems to give the following error:
"Error reading from drive B: DOS area: drive not ready
  (A)bort, (I)gnore, (R)etry, (F)ail.

Situation:
Under VmWare Workstation 7.04 (Win64), a single floppydrive with  inside 
it a 1.44MB diskette with Syslinux 4.04 on it. This Syslinux bootloader 
loads MEMDISK, then a 360KB bootable image located on the diskette. The 
360KB image becomes A:, meanwhile pushing real diskette from which it 
loaded, back to B:.
Trying to perform B: (or DIR B:) triggers the error.

Troubleshooting steps taken so far:
* replace the 360KB FreeDOS image file by a MSDOS 7.10 one (take 
bootdisk, open in WinImage, delete everything besides kernel and shell, 
defragment image, convert to 360KB, save) works flawlessly, can issue a 
DIR B: and see Syslinux files, the 360KB image, everything.
* booting the 360KB FreeDOS image from Syslinux 4.04 on harddisk then do 
B: works fine
* booting the 360KB FreeDOS image from Syslinux 4.04 on CDROM then do B: 
works fine
* try older MEMDISK from Syslinux 3.86

What I've not done yet:
* replace Syslinux 4.04 by Syslinux 3.86 , I remember old Syslinux 
worked fine, allowing to save space by SHELL=B:\COMMAND.COM B:\ 
/P=B:\AUTOEXEC.BAT for example or DISKCOPY A: B:\FDBOOT.IMG /O /G /X

As MSDOS doesn't have this issue I'd guess it's a FreeDOS kernel bug, 
maybe some disk shuffling problem

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel

Reply via email to