I tested EMM386 "horse" with VDS option, and on this system it's still
total meltdown. All hard drive info misreported. Too scared to continue
in case can't boot anymore.
Asus A7V333 latest BIOS
Adaptec 29160N SCSI host adapter with 2 x 36Gb drives
FreeDOS Beta9sr1 except HIMEM64 3.10a and EMM386 "horse"
FDISK and PQMAGIC claim there are no partitions defined and give totally
crazy readings for physical disk sizes.
FDCONFIG.SYS follows (look out for line wrap):
; rem FDXMS gives VDISK error on some soft reboots
; rem FDXMS gives warning about an interrupt not being supported by EMM386
DEVICE=DRIVER\HIMEM.EXE /NOABOVE16 /X
; rem VDS option with EMM386 v2.03 corrupts everything
; rem TESTING VDS option with EMM386 "horse"
DEVICE=TESTING\EMM386.EXE NOEMS VDS X=TEST /verbose
; rem UMBPCI found to be more stable for UMBs on every system tested
rem Load the SCSI for 29160N card, wait, we're using INT13 instead!
rem UDMA hard drives, don't have any non-SCSI drives in this system
rem Why do some people run non-SCSI drives?
rem This is not open source!
rem This is Microsoft, yikes
devicehigh=OTHER\ramdrive.sys 4096 512 1024 /e
rem This is version from MSCLIENT 3.0, look out for version mismatch
rem lbacache tuns switch is needed for SCSI and UMBPCI
rem but it doesn't seem to be needed on the 29360N card
SHELL=COMMAND.COM A:\ /E:1024 /F /MSG /P=.\FREEDOS\FDAUTO.BAT
Gerry Hickman (London UK)
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
Freedos-user mailing list