I suspected as much. Dell support, of course, runs and hides when it comes
to any issue outside the Microsoft ecosystem. So, no joy there.
Thanks for your time and prompt reply, Tom.
On Mon, Jan 6, 2020 at 1:30 PM tom ehlert wrote:
> Hallo Herr Jack Browning,
>
> am Montag, 6. Janua
I've been trying to update the BIOS on my wife's Dell Inspiron 17 5721
laptop using FreeDOS. I've tried to do this with FreeDOS 1.0, 1.1, 1.2, and
1.3rc2, each time with the same result.
What happens is this: after setting up FreeDOS on a USB stick using its
.img file (and adding the BIOS
Note the following comments by Rugxulo in this post:
www.bttr-software.de/forum/forum_entry.php?id=14140
* If you want to try his latest drivers (Mar-18) [sic], grab them from
* his DropBox, but since he doesn't even use FreeDOS (only MS-DOS 6.22),
* I'm not sure if they work at all anymore:
And
questions/comments to me. I
now regard it as defunct, and you now know why.
Jack R. Ellis
--
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https
of that, as well! Although I was
tired of Rugxulo's never-ending upgrade-Upgrade-UPGRADE E-Mails, did
he really believe I would not have listened to a SERIOUS bug comment
about a PC-compatible system? I surely WOULD have!
* (08-Dec-2014) Jim Hall: I see Jack has got you involved on this too.
* He's becoming
Johnson Lam has posted a new DRIVERS.ZIP file, now dated 19-Oct-2014 and
with an updated UHDD driver, in his dropbox at:
http://dl.dropboxusercontent.com/u/15785527/drivers.zip
No change to any of the other drivers but re-dating them 19-Oct-2014 for
consistency, also no change to the /B stand
BAD year for illness re: my surgery in May and re: Johnson Lam having
a nasty Flu last week. Johnson is finally O.K., and he has posted a
new 27-Sep-2014 DRIVERS.ZIP file with an upgraded UHDD driver, in his
dropbox at:
http://dl.dropboxusercontent.com/u/15785527/drivers.zip
No changes to the
My belated reply to an FD-User post by Bill Haught, dated 2014-07-18
12:36:17 and answered below by Tom Ehlert. I planned to stay silent,
but all of the following BEGS to be addressed! --
As I mentioned earlier, Freedos requires a ATA legacy mode in BIOS,
which I don't have.
wrong.
Tom is
At 08:46 AM 7/11/2014, panyong wrote:
Hi,
I installed FreeDOS1.1 on Parallels , and i want to install some
software on the list
http://www.freedos.org/software/
I¡¯ve tried to use a browser , but there is no on freedos . I've
also tried using the usb-flash-disk to share a file , but i fail
I've noticed a difference in command line parsing between FreeDOS and PC-DOS.
Both FreeDOS and PC-DOS put the command line, starting with the character
after the executable, in a buffer at offset 0x80 in the PSP.
The behavior difference I see with FreeDOS is if the first non-blank
character
An off-topic addendum to my 2011 post on this forum about U.S. medicine --
Regrettably, I have been diagnosed with a 98% chance of bladder cancer, for
unknown reasons excepting bad luck. I was told it needs to be taken care
of within 3 months, after being detected on 4-Mar-2014.I do not
Johnson Lam has posted a new 26-Jan-2014 DRIVERS.ZIP file, with a
corrected UIDE and an upgraded UHDD/UDVD2, in his dropbox at --
http://dl.dropboxusercontent.com/u/15785527/drivers.zip
UIDE had an error in its /B stand alone driver, which would not
ignore CD/DVD media changes as it should.
you. ;)
... In any case, I wanted to get multi-caching done in UIDE, while
I still had some ideas about HOW to do it!!
Enjoy 2014 in good health Jack! Thanks for updating your work.
You are most welcome, Bernd, and my Thanks for your nice comments!
Jack R. Ellis
when RDISK is patched for 4-GB!
Jack R. Ellis
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue
Johnson Lam has posted a new 12-Dec-2013 DRIVERS.ZIP update in
his dropbox at:
http://dl.dropboxusercontent.com/u/15785527/drivers.zip
UIDE now offers a separate CD/DVD cache, with a /C switch, for
users with an old CD drive requiring limited seeks, to avoid
tracking errors and low speed.
!V6.22 MS-DOS and V4.0
Win/NT also save poor-old retirees like me from paying $500/year
tribute to Gates Co. for their semi-annual collection of new
BUGS, which they call service packs!
BEST wishes,
Jack R. Ellis
It's really too bad, though, that MS won't make it official and release
the MS-DOS source as public domain, or at least one of the various
open-source licenses.
Surely you JEST!, my friend [are joking]! Gates Co. are charter
members of the U.S.A.'s All we want is MONEY! brotherhood!
The UIDE drivers have all been updated to 14-Nov-2013, and they are
now available from Johnson Lam's dropbox at --
http://dl.dropboxusercontent.com/u/15785527/drivers.zip
In this update, UHDD and UDVD2 no-longer support private caches for
user drivers. Reasons for this are a bit involved --
Re: Rugxulo's FreeDOS front-page comment about Another week, another
UIDE update, I want to assure people that, despite now being age 68,
I am NOT losing my mind!
The 20-Aug-13 update was to provide CD/DVD kiosk users in Hong Kong
(and elsewhere) a way to cache CD/DVD data without loading the
, as before.
Users who do not desire disk/diskette handling can minimize
UHDD with its /N1 switch. This saves 848 bytes, and it will
make UHDD into a small cache-only driver. For CD/DVD only
or other such systems desiring only one cache, UDVD2 can omit
/N and simply run on UHDD's cache, as before.
Jack
My apologies -- In my earlier E-Mail today about UDVD2/
UHDD, I meant to say: For 'CD/DVD only' or other such
systems desiring only one cache, UDVD2 can omit /S [not
/N] and simply run on UHDD's cache, as before.
--
An IMPORTANT note on using UHDD/UIDE, which I felt needed to be posted --
Protected mode users (JEMM386, EMM386, etc.) who run UHDD or UIDE should
load these drivers with their /F switch. For caches of 80-MB to 1023-MB,
/F causes UHDD/UIDE to have 64K cache blocks, not 16K blocks. 64K blocks
A++ would read again
For all those of us who do not speak Germanicized English,
would you care to say EXACTLY what-in-HELL the above means??
Regards from our Bunch of Trolls That Ruin (TM)
And Greetings to you, Mr. Junior Troll (VERY junior,
indeed!). I see you must have learned NOTHING,
I don't know ...
Well, Mike, at least you ADMIT to it!
... but if there was a utility to analyze the tone and content
of messages and rank them I think that a lot of your messages
to this list would be labeled aggressive/hostile.
Tough tomatoes. If you don't like my tone, for which I
of its pundits ever again!!
Jack R. Ellis
=
Original Message
Subject: Problem with the UIDE Cache and LS120 Diskette Drives.
Date: Thu, 11 Oct 2012 20:03:58 +
From: MR-LEGO mr-lego...@web.de
THEMSELVES what those rules ARE!!
And now, Bret, DO NOT merely spout your own propaganda again! If
you have more to say, speak to the points -- SPEAK TO THE POINTS! --
that I have listed above!!
And do so in private, as after this E-Mail, I will again unsubscribe
from FD-User.Jack is right
I was about to post bugreport at VirtualBox bugtracker, but decided to
double-check the issue first. On my system floppy images change are
correctly recognized. VirtualBox 4.1.4-3.2.3 OSE OpenSUSE 12.1.
The issue is that VirtualBox is not posting diskette media-change
status in the BIOS data
of
debugging the problem but finds a lot of time to write loong
emails
To which I shall add: Maybe you might have read the UIDE.ASM file
before making any BASELESS and WRONG accusations about my drivers!
Jack R. Ellis
as-is. If
users want to run VirtualBox, they can simply use UIDE/UIDE2 /E which
specifies 'hands off those floppies' (like Tom stated above), exactly
as the writers of VirtualBox intended! No diskette data errors, and
everybody should be happy!
Jack R. Ellis
UIDE has NEVER ignored if a diskette has change-line support! It
does in fact check the BIOS data table at 0:48Fh for bit 0 (change
line for diskette A:) or bit 4 (change line for diskette B:). If
those bits are off, diskette A: or diskette B: will not be cached.
That is an interesting
It's not impossible to cache floppies, Jack. You just need to do it
differently than you're doing now ...
Back in 1980, I told an old friend of mine about a 750K video-driver
package which I had seen (written in C, of course!), and he noted,
They've got GUTS, calling that a DRIVER!
If I had
You are WRONG, Tom!!
Is he ? or are you being RUDE, Jack?
Tom could have written me privately, before publicly saying UIDE
assumes change-line support, but did not. I responded in kind!
Not Tom, but I'd like to learn from /what exact source/ you got the
definition for those bits.
My
Jack, PLEASE, don't pull yourself up on the VirtualBox issue, it is
rather a more general problem.
You simply rely on the contents of the memory region rather than than
properly query system via INT13. And that isn't adding much to the
logic and overall size of your drivers compared
/UIDE2's diskette I-O has never been a problem BUT
for VirtualBox, I will keep UIDE/UIDE2 as-is. VirtualBox users
now have the /E switch they can specify with my drivers, and all
other users of hardware PCs and (NOT so flaky) hardware change
lines will continue to run just fine!
Jack R. Ellis
As I just got through noting, in another post, why would the BIOS
data include diskette change-line flags if they were NOT intended
to be USED??
Until someone can positively REFUTE the data offered by the BIOS
Central data-table list, my opinion is that neither you nor any-
one else can say
damn ex-wife never did [part of
why she BECAME my ex- 32 years ago!!], that I have a REASON
for everything I say and do, same as for everything in UIDE
and UIDE2!!
Jack R. Ellis
--
Live Security Virtual Conference
who
use VirtualBox or other imperfect garbage, who do not like
having to forego some UIDE drive caching by using the above,
should damned-well INSIST that VirtualBox etc. gets FIXED!
I am VERY TIRED of having to add Band Aids into my drivers
to deal with the FOOLISH errors of OTHERS!!
Jack R. Ellis
The FAT file system is defined by DOS, and I want UIDE/UIDE2 to
have NO run-time dependencies on the DOS system.
Nice in theory, but unfortunately doesn't work in practice.
Sure seems to, since before this thread, UIDE/UIDE2 have trapped only
BIOS Int 13h I-O requests, and no one has ever
the same initialization functions. A few differences re: how
they allocate XMS memory and where they load, but their device
scanning and setup is 100% the same.
Jack R. Ellis
--
Live Security Virtual Conference
Exclusive live
-- UIDE2 has only 16 spare bytes before it goes back over a 7K
.SYS file! But, I shall find a way!
I've never looked at UIDE closely, but there's always room for space
improvement in assembly!! ;-)
Maybe you should look again at the UIDE.ASM source file! I have
boiled down its logic
Bertho,
Given the high level of responsibility [Ha-Ha!] taken by the
VirtualBox creators, it looks as if I will have to add another
UIDE switch, that disables diskette caching regardless of what
its other switches tell it to do.
Jack, if I may chime in... I think you're now contemplating
shall ALWAYS follow it!
Jack R. Ellis
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
! I get few positive comments about UIDE --
people appear to take it for granted, I guess -- and I do appreciate
your thoughts!
Jack R. Ellis
--
Live Security Virtual Conference
Exclusive live event will cover all
and I (perhaps others
as well) to make changes in long-established programs just for them!!
Jack R. Ellis
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat
cache and prevent the
same diskette problem from occurring.
Jack R. Ellis
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how
) and then again running
with UIDEJR (no cache). If there is no speed change, your host
likely is doing caching, and you may not need my drivers at all.
Jack R. Ellis
--
Live Security Virtual Conference
Exclusive live event
another LONG chat! with the creators of Virtual
Box, who seem to live in their own world and seem to IGNORE a lot of
pre-existing PC hardware conventions Whenever it suits them!.
Jack R. Ellis
--
Live Security Virtual
On Tue, 10 Apr 2012 22:16:50 -0700, Ralf A. Quint free...@gmx.net wrote:
At 01:13 PM 4/10/2012, Jack wrote:
Cannot answer on all subjects, but re: disk/CD/DVD drivers, I am NOT
overly optimistic! Intel/Microsoft want us all to buy into AHCI,
and they may have started ordering mainboard
This topic is not about DOS vs other operating systems, or the fact
that users tend to gradually abandon DOS. It's about the survivability
of DOS vis-a-vis hardware ... What will happen with future development
of the hardware architectures?
Cannot answer on all subjects, but re: disk/CD/DVD
Johnson Lam has posted a new DRIVERS.ZIP file, now dated
23-Mar-2012, on his website at:
http://johnson.tmfc.net/dos/driver.html
The UIDE and UIDE2 drivers now use only 912 bytes of upper-
or DOS memory with their /H switch!To do this, UIDE now
runs 30 BIOS units (was 34) same as UIDE2, and
VERY funny off topic, overheard today, which I just HAVE to share --
What does a U.S. Age-20s Slept Thru High-School type, too old to say
The dog ate my homework!!, try to tell our apartment manager re: why
he cannot help with his girlfriend's 3-week late rent??
The ATM ate my check!!
A
!
They remind me of the old Jason Robards and Barbara Harris movie titled
A Thousand Clowns!
Best wishes,
Jack R. Ellis
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu
We need NO more hardware, CERTAINLY NOT any damned 64-bitters
having 64-GB of memory, when in fact Intel/Microsoft never REALLY
learned to use 32-bit or even 16-bit systems all that well! ...
I agree, but nobody else does ... Perhaps you should read what
Niklaus Wirth had to say back in
years.
I must conclude that the problems you are seeing, using JEMMEX
and UIDE2, are NOT caused by those drivers.
Jack R. Ellis
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http
Problem (seems to be) solved. Formerly I was using a line:
INSTALLHIGH=C:\FDOS\BIN\UIDE2.SYS
...and this gave problems. When I replaced INSTALLHIGH with
DEVICEHIGH -- there are no problems anymore.
I thought, that INSTALL and DEVICE keywords are synonyms for
fdconfig.sys file, since I
must
use a DEVLOAD command in AUTOEXEC, if you want UIDE2 to
run with FreeDOS from the HMA. Then, you will be able
to amaze friends with your only 928-byte disk/CD/DVD/
caching driver -- Just tell them you know a Sorcerer!
Best wishes,
Jack R. Ellis
filename logic limiting its HMA!
The UIDE driver has no such HMA limits, as it places
its binary-search table in XMS memory.
Jack R. Ellis
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http
to
be seen as a bit more evil, I say Witch Doctor or Hoodoo Man!!
Best wishes,
Jack R. Ellis
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
Actually, it was a bit surprising to me that I still need a software
cache ... Well, perhaps the NVIDIA SATA isn't the best fit for DOS.
DOS doesn't use SATA anyways (AFAIK), only IDE compatibility mode.
It would be even slower without UDMA or a software cache. As to
why you need it, it's
I have saved XMGR for real mode users who run UMBBCI first, followed
by XMGR. In that case, XMGR is able to read UMBPCI's table of UMBs
and can load there directly, which also uses 0 low-memory like JEMMEX.
...
Unless you need EMS, you don't truly need JEMMEX itself ...
JEMMEX/JEMM386
DOS doesn't use SATA anyways (AFAIK), only IDE compatibility mode.
It's still much faster than the hardware, that I was using in
1991. The HDD itself has quite large hardware cache (16 MB -
incredibly large space compared to 640 KB).
Hard-disks have come a long way. In 1994, I paid $350
I noticed that pauses while using edit shipped with FreeDOS
- can it really be that slow when saving edited file?
Try using EDIT shipped with V6.22 or V7.10 MS-DOS, which I
find is not too bad!
--
This SF email is
Unless you need EMS, you don't truly need JEMMEX itself. Last
I checked, I don't think it would let you run XMS only unless
you did NOEMS, and even that still left you in V86 mode.
To test this, I change the first few lines of my CONFIG.SYS file
which are --
DEVICE=C:\BIN\UMBPCI.SYS
Rugxulo, I REALLY think you should check AGAIN running JEMM386
without NOEMS -- worked fine for me!
In the past I always had EMM386 enabled, and it worked fine. In fact,
some apps explicitly needed EMS and/or EMM386. But nowadays, FreeDOS
is so good at keep low RAM free that I don't need
Intel giveth NOTHING, and followeth only All we want is MONEY!,
same as Gates Co.! In my opinion, absolutely NO excuse for AHCI
that a better-written Windows driver could NOT have solved, but for
Intel as-always wanting to sell-Sell-SELL new chips!
In fairness, not every person is truly
JEMMEX/JEMM386 also allow VCPI/DPMI to be used,
VCPI, yes, but not DPMI, you don't (necessarily) need EMM386 for that.
Same for VCPI, I suppose -- There are subroutine packages that set up
VCPI for a user application, if needed.
they allow mapping of
upper-memory addresses into UMBs that
Johnson Lam has posted a new 7-Mar-2012 DRIVERS.ZIP
file with a much smaller UIDE2, on his website at:
http://johnson.tmfc.net/dos/driver.html
The UIDE2 driver, for faster speed with a protected
mode system (JEMM386/JEMMEX etc.), is now less than
7K bytes in size! To achieve this, I needed to
breaks?? Does it
display its title message and controller/device data, or does it
simply crash?? Let me know.
Jack R. Ellis
--
Virtualization Cloud Management Using Capacity Planning
Cloud computing makes use
, there is no further need for a large number of
DOS buffers. UIDE does a much better caching job than the old DOS
buffers, and by reducing your buffer count, you may save enough HMA
space to put UIDE up there in the HMA, as well!
Best wishes,
Jack R. Ellis
through UIDE, or
(B) vice-versa, i.e. you must load UIDE with /N2 to avoid your Ghost
errors. NOT any fun, either way, I know! But, I have never used
Ghost and do not know what its writers do in running CD/DVD drives!
Best wishes,
Jack R. Ellis
Johnson Lam has posted a new DRIVERS.ZIP dated 24-Feb-2012 on
his website at http://johnson.tmfc.net/dos/drivers.html.
In it, UIDE and UIDE2 are corrected so that they again handle
64K UltraDMA boundaries properly. A user I-O buffer which
crosses-over a 64K address boundary will cause the
In my previous post about the new 24-Feb-2012 UIDE/UIDE2
drivers, I mistyped Johnson Lam's URL with an extra s!
The correct URL for the new drivers is --
http://johnson.tmfc.net/dos/driver.html
My apologies -- Age 66 is SO much fun! as I often say!
A Heads Up (warning) message to all users of UIDE and UIDE2 --
Some time ago, I considered Read-Ahead for UIDE/UIDE2. But effective
Read-Ahead requires knowing file sizes, to prevent reading too FAR ahead
and losing time! File sizes demand DOS calls, and I want UIDE/UIDE2 to
remain generic
Jack has his own private reasons for not being a fan of ASPI, thus his
UIDE driver (PCI IDE/SATA storage and optical disk driver) doesn't
implement nor hook into ASPI. I'm not aware of opensource CD-writing
software that doesn't require ASPI.
Not entirely true -- UIDE can call Int 13h
I knew this would provoke a comment from you, Jack.
Yes, you always were a provoker, weren't you, Bret?
The purpose of a cache is to put as much data in RAM as it can, so that
the disk is accessed as little as possible. It's true that the cached
data does eventually get written to disk
Re: 4K sector sizes, I realized today that UIDE, UIDE2,
and UIDEJR likely will NOT be affected at all --
1) DOS has a 64K-byte limit for read/write requests, in
fact 127 sectors of 512 bytes (the UIDE drivers do
accept 128). Since 4K-byte sectors fit into this
limit, no
To set the record straight on caches and on UIDE --
Can you recommend any free int 13 or block device based delayed/
pooled write caching software? As far as I can remember, all
modern (LBA compatible, given disk sizes on current PCs)
implementations of this are commercial.
I don't know
For what it is worth, my take on 4K-byte (or other-than-512
byte) sectors for DOS systems is very-much the same as Eric's
and I shall reply to some comments from one of his posts --
Also depending on your BIOS, you could have a limit of at
most 2^28, 2^32 or 2^48 sectors per disk ...
Not a
Anybody has an idea how to solve this with free software? Would the
eltorito.sys driver help?
Wasn't the solution to enable IO APIC or something like that? So a
different enabled chipset.
ELTORITO.SYS can help, but only if you configure the VM to start with
booting from CD, after which
1. Would like to ask how much memory does FreeDOS support, e.g. 4 GiB?
Yes you'll be limited to a maximum of 4GB if you have 4GB or more. In
practice this maximum could be anywhere between 2GB and 4GB (usually
3.3GB or 3.5GB) due to PCI chipset device mapping into the top of memory.
On older
-boot for Windows/NT,
but with some knowledge and research, any DOS can be made to work!
I hope this helps you!
Jack R. Ellis
--
All the data continuously generated in your IT infrastructure
contains a definitive record
On the topic of wear leveling I would go with the DOM products, as
they are designed as hard drive replacements. It's pretty easy to
burn up FLASH so wear leveling is important.
FWIW, they claim that FLASH has unlimited read capability, but is
limited in the number of writes. So, at
like me, a garden variety $40 hard disk should do just fine WITHOUT
any such concerns!
Jack R. Ellis
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
that they really
should not need caching. You can then run UIDE with its /N1 switch
which causes it to ignore hard-disks but continue to cache diskettes
and CD/DVD drives. They need caching, for they are otherwise SLOW!
Jack R. Ellis
peoples' attention, but in the wrong way. THANK YOU for your insight,
in the same sense as Captain Armstrong [in your 1980s Anzacs series],
who initially addressed his all-volunteer platoon by saying, You shall
be treated as intelligent adults!
Jack R. Ellis
It is VERY TIRESOME, having to respond to posts on this board with
I DID NOT say ... or I DO NOT agree ..., when one's REAL words
are either misunderstood or often TWISTED for some other agenda!
Many such replies would cause their writers to FAIL, QUICKLY, in
almost all U.S. High-School Debate
their users Know what they are doing!
As all options, the user has to decide whether to use that, yes.
How carefully you avoid my problematical comment!
Jack R. Ellis
--
The demand for IT networking professionals continues
MS-DOS, even
despite my many-other thoughts about Gates Flunkeys -- He and
all his F's in fact DO handle A20 as their XMS specs recommend!
Jack R. Ellis
--
The demand for IT networking professionals continues to grow
will use
JEMM386, which I consider to be FAR superior and always WILL be!
Jack R. Ellis
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more
are not, but a few are. Read the JEMM ChangeLog, then you
can decide which hardware-dependent problems might have affected
its predecessor FD-EMM386.
Jack R. Ellis
--
The demand for IT networking professionals continues to grow
and is completely
unheard of ...
I suggest that a lot of other things besides the A20 line could
have caused such a problem. In my opinion, you need quite a bit
more evidence, BEFORE you can fault the A20 line only because
your crash appeared to occur with only XMS!!
Jack R. Ellis
In my previous post about FD-EMM386 being changed to JEMM386, and
to be perfectly clear, those Flat-Ass DISASTERS I noted are not
at ALL in JEMM386 but are in FD-EMM386 and had to be CORRECTED by
Japheth! Sorry for any confusion caused by me -- JEMM386/JEMMEX
ARE the EMM drivers of choice, in
has become
just as problematical as some of the A20 issues themselves!].
Jack R. Ellis
--
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more
I am DISMAYED by some of the recent comments on this board
regarding old EMM386 v.s. JEMM386/JEMMEX, the A20 line
etc.!
First, I use and recommend JEMM386/JEMMEX with my UIDE and
other drivers. I absolutely REFUSE using old EMM386 by
Gates Co. because it has (A) Never-fixed BUGS in its VDS
Johnson Lam has posted a new 16-Oct-2011 DRIVERS.ZIP file on
his website at http://johnson.tmfc.net/dos/driver.html.
In it, UIDE has again been reduced down to a 7.5K-byte file,
same as UIDE2, for boot diskettes and other systems having
limited space.So, UIDE-S is no longer needed, and it
Johnson Lam has posted an updated 7-Oct-2011 DRIVERS.ZIP file on
his website, at http://johnson.tmfc.net/dos/driver.html. The
site still has a Last Update date of 9-30, but the files which
download ARE dated 10-07-2011 and have been verified O.K.
This update is not more driver improvements but
of (A) using XMS memory as a
buffer for UltraDMA I-O which is misaligned or crosses
a 64K boundary, and (B) using free HMA space to save
upper/DOS memory and putting much of my drivers there!
Tom is often quiet in the background, but when he DOES
speak, it MATTERS!
Jack R. Ellis
Johnson Lam has posted a new 30-Sep-2011 DRIVERS.ZIP file on
his website at http://johnson.tmfc.net/dos/driver.html.
The UIDE, UIDE2 and UIDE-S drivers can now be assembled from
the UIDE.ASM source file, using a /dPMDVR switch for UIDE2
and a /dMINDVR switch for UIDE-S (protected or minimum
Johnson Lam has posted an updated 23-Sep-2011 DRIVERS.ZIP file, with all
UIDE drivers improved, on his website at --
http://johnson.tmfc.net/dos/driver.html
UIDE-S now runs 30 BIOS disks/diskettes and 8 CD/DVD drives, and it also
sets the UIDE$ default name when no CD/DVD drives are found,
Johnson Lam has posted an updated 9-Sep-2011 DRIVERS.ZIP file, on his
website at johnson.tmfc.net/dos/driver.html, which contains a new
UIDE2, also updates to the other UIDE drivers.
UIDE2 uses old-style protected mode caching, that was in UIDE until
August, 2010. Try as I may, I simply cannot
1 - 100 of 167 matches
Mail list logo
