Op 24-7-2011 16:52, Jack schreef:
> Apologies for my "late" response re: UIDE v.s. VirtualBox. Had to have
> my (infected!) gall-bladder removed, 25-Jun-2011. NASTY episode, and I
> am still recovering and "moving a bit slow" on driver work! Re: recent
> EDR-DOS forum posts, I say the same as our author Mark Twain once did --
> "The rumors of my demise are greatly exaggerated"!
Goodluck recovering, Jack.
> So, I have added a /E ("emulator") switch to UIDE and UIDE-S. /E makes
> the drivers "call the BIOS" on every hard disk I-O request. This means
> UIDE can "go around" most of its hard-disk setup logic and simply assume
> the BIOS "knows what it is doing" with disk drives. CD/DVD drives that
> were never part of the PC BIOS still require UIDE's setup logic to work,
> or they will not get "detected" and used. /E causes a minor speed loss
> (5% or less) in UIDE's cache speed, due to calling another "driver" (the
> BIOS) and since disks will be unable to use UIDE's XMS cache buffers for
> direct I-O. But, unlike /N1 which totally ignores hard disks, /E still
> allows hard-disk data to be cached after BIOS I-O requests, and it ought
> to let VirtualBox run O.K. with UIDE and UIDE-S. I don't use and don't
> want VirtualBox, so I must let users tell me if /E works as intended.
Thanks very much for adding this. I can't promise any testing of this in
the short run, but hope mr Juan Castro is able to as he started this
thread. In the end I might test my complete FreeDOS CD on multiple
emulators and physical hardware to catch any remaining issues. For now
sticking to VMware.
Juan, could you please try these drivers either by emailing Jack or
waiting till Johnson Lam has posted them at
DEVICE=C:\FDOS\BIN\UIDE.SYS /D:FDCD0001 /S5 /E
(without enabling I/O-APIC and ICH9 chipset as Jeremy Davis posted
earlier, thus resorting to normal APIC and PIIX3 chipset from Intel
440FX Pentium-Pro or P2 motherboards)
These emulator-specific hacks are slightly annoying though, EMM386/JEMM
has (had) them as well due to a VMware specific memory region being in
use. Installation routines having to detect PCI-based devices (mainly
videocards) might do the trick but involve extra work.
I'm sticking to the /S5 parameter in general for automated UIDE as only
absolute numbers are possible, no percentages (/S50% or /S0.5) with
truncating (taking intended minimum amounts in account, e.g
n=5/15/25/40/50 or 80<=n<=4093 minus PCI mapped space)
> Jack R. Ellis
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
Freedos-user mailing list