Re: [Freedos-user] "Test." -- does that come from FreeDOS?

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

[Freedos-user] "Test." -- does that come from FreeDOS?

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 executab

Re: [Freedos-user] Rugxulo IS A FRAUD!!!

To all on this forum who say "Calmaros" [Lets be calm] etc., read THIS: In 1975. 1977, 1979, and 1981, I was declared DEAD by my parents, after a RIDICULOUS and totally WRONG comment from my sister in 1975, and also over my converting from Judaism to Episcopalianism in 1974. They died in 1987 (m

[Freedos-user] Rugxulo IS A FRAUD!!!

Note the following comments by Rugxulo in this post: * 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 note the following comments by Rugxulo in this post

Re: [Freedos-user] XIDE Updated; UIDE Support TERMINATED!

t;newer" * drivers and report back because they didn't work for me (refused to * boot on Lenovo 2011 ... The above is the first I ever heard of that, as well! Although I was tired of Rugxulo's never-ending "upgrade-Upgrade-UPGRADE" E-Mails, did he really believe I would no

[Freedos-user] XIDE Updated; UIDE Support TERMINATED!

ACKSTABBING! XIDE will remain closed-source and I plan NEVER to do any more open-source work: Too many absolute FREAKS and "MAD Dogs!" to put-up with!! Please do NOT address any further UIDE questions/comments to me. I now regard it as "defunct", and you now know why.

[Freedos-user] New 19-Oct-2014 Drivers -- Faster UHDD!

Johnson Lam has posted a new DRIVERS.ZIP file, now dated 19-Oct-2014 and with an updated UHDD driver, in his "dropbox" at: No change to any of the other drivers but re-dating them 19-Oct-2014 for consistency, also no change to the /B "sta

[Freedos-user] New 27-Sep-2014 Drivers -- UHDD Updated.

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: No changes to t

[Freedos-user] Using UIDE/UHDD With FreeDOS.

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.

Re: [Freedos-user] Help Using FreeDOS1.1

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 ag

[Freedos-user] Off-Topic: Recovering From The HOSPITAL!!

My Thanks to Rugxulo, DOS386, and others on this forum for their good wishes about my prostate surgery. I am told by my surgeon that I have NO cancer, neither bladder nor prostate, and I shall be "with you" for a while longer. But in fact, it was the WORST medical experience of my life! I told

[Freedos-user] Command Line Parsing

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 aft

[Freedos-user] SERIOUS Off-Topic, Part 2 -- U.S. Medicine.

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 d

[Freedos-user] Updated UHDD/UDVD2 Drivers: Caching Re-Added.

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 -- UIDE had an error in its /B "stand alone" driver, which would not ignore CD/DVD media changes as it should.

Re: [Freedos-user] New 12-Jan-2014 UIDE, With 4 Caches!

re possible, but not all DOS systems work with them -- V6.22 MS-DOS "CHKDSK" CRASHES when RDISK is patched for 4-GB! Jack R. Ellis -- Rapidly troubleshoot problems before they affect your business. Most IT org

Re: [Freedos-user] New 12-Jan-2014 UIDE, With 4 Caches!

plus any "user driver" caches, must total 4-GB or less! Sorry if that disappoints 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 updatin

[Freedos-user] New 12-Jan-2014 UIDE, With 4 Caches!

Johnson Lam has posted a new 12-Jan-2014 DRIVERS.ZIP file, with an updated UIDE and re-issued UHDD/UDVD2, in his "dropbox" at -- The file is "postdated" 12-Jan-2014 as Johnson is VERY busy at his job, but he has managed to post it early.

[Freedos-user] New 12-Dec-2013 UIDE Driver.

Johnson Lam has posted a new 12-Dec-2013 DRIVERS.ZIP update in his "dropbox" at: 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.

Re: [Freedos-user] "LBA" And FreeDOS.

al in pc after all. A pleasure to know you, dear Lady, after all my dealings on this forum with "legalists" who FAIL to see that I was only giving an EXAMPLE of V7.10 still being available!V6.22 MS-DOS and V4.0 Win/NT also save poor-old retirees li

Re: [Freedos-user] "LBA" And FreeDOS.

legal. As I said, I will not argue the legalities, since you indicate that they are "murky" at best when applied to "abandonware" like MS-DOS. I only wanted to give an example of V7.10 MS-DOS still being avail- able for use. Further debate about its availability being "legal

Re: [Freedos-user] "LBA" And FreeDOS.

t;> And re: your comment that "You can't 'freely' download, modify >> or redistribute any DOS besides FreeDOS", I can only say again >> that the above website most-certainly DID work for me! > > Freely in this contex

Re: [Freedos-user] "LBA" And FreeDOS.

Rugxulo, Re: your recent posts, I will summarize my feeling as follows: "LZ-DOS" and other copies of V7.10 MS-DOS are still available. You may not consider it reliable, and Dennis may have some odd problem accessing it, but that website did give me, on 5-Dec-2013, a work

Re: [Freedos-user] "LBA" And FreeDOS.

> The ms-dos7.ht.bg site seems to have been offline since 2010 ... Oh, REALLY?? Sure worked well for me yesterday, 4-Dec-2013, when I got both V7.10 MS-DOS diskettes and checked them! And it also caused me no problems when I accessed the site again, a moment ago!!

Re: [Freedos-user] "LBA" And FreeDOS.

> 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!" brotherhoo

Re: [Freedos-user] "LBA" And FreeDOS.

recommending that FreeDOS "advertise" or support ANY other DOS variants -- I am simply saying that V7.10 MS-DOS is in fact still available, as at-least the website I note above should prove to you. > It would be fa

[Freedos-user] "LBA" And FreeDOS.

Note on the FreeDOS "main page" that there are comments about FreeDOS offering "LBA" large-disk capability (48-bit disk addressing, not 24- bit "CHS"), which MS-DOS did not have, and which the "main page" says was unavailable except with DOS Windows. NOT quite true! From having written and teste

[Freedos-user] New 14-Nov-2013 UHDD/UDVD2 -- Private Caches Deleted.

The "UIDE" drivers have all been updated to 14-Nov-2013, and they are now available from Johnson Lam's "dropbox" at -- In this update, UHDD and UDVD2 no-longer support "private" caches for user drivers. Reasons for this are a bit "involv

[Freedos-user] UIDE Updates: NOT "Losing My Mind"!

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 t

Re: [Freedos-user] New UHDD/UDVD2 -- A "Clarification"!

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." -- Le

[Freedos-user] New UHDD/UDVD2 -- A "Clarification"!

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 R. Ellis -- Learn the latest--Visua

[Freedos-user] Using UHDD/UIDE In "Protected Mode".

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 block

Re: [Freedos-user] DISGUSTED With "Pundits"!!

> 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

Re: [Freedos-user] DISGUSTED With "Pundits"!!

> 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 N

[Freedos-user] DISGUSTED With "Pundits"!!

ll again "unsubscribe" from FD-User. And I hope NO ONE expects me to listen to any of its "pundits" ever again!! Jack R. Ellis = Original Message Subject: Problem with the UIDE Cach

Re: [Freedos-user] UIDE Diskette "Change Line Capability" Tests.

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 and everyone else is an idiot", "Are you trying to prove yourself smarter than everyone else", plus other such INSULTS will be ENOUGH

[Freedos-user] UIDE Diskette "Change Line Capability" Tests.

Re: the thread on this forum about how to test if a diskette will support a "media change line", I offer the following: My system has an old 2007 single-CPU Biostar mainboard with a VIA 8237 controller (VIA has now just-about quit offering chipsets!). My BIOS is from Phoenix and is dated 11-Jan-20

Re: [Freedos-user] checking virtualbox source codes for floppy and pci speed issues

es) runs almost instantaneously, so I see no reason to change THAT logic in UIDE/UIDE2, either! You also MIGHT hear from VirtualBox that their setup of 0:048Fh is in fact CORRECT and some OTHER element of their program is LOSING the byte! I.E. they DID intend diskettes to provide change-line support,

Re: [Freedos-user] checking virtualbox source codes for floppy and pci speed issues

ED bit at 0:048Fh!! How INTERESTING!! NOT including you, Eric, who took the time to "find out" all of the above, but I think there are many God-DAMNED BUFFOONS on this forum who owe ME an APOLOGY Jack R. Ellis

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

>> 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

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

Cs and (NOT so "flaky") hardware change lines will continue to run just fine! Jack R. Ellis -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threa

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> 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

Re: [Freedos-user] Virtual floppy change problem

>> 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 > de

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> to make a long answer short: > in VirtualBox, 40:8f is 00 > again, clearly stating 'change line is not supported' Maybe for your system, obviously not on Wolfgang's, and who-knows re: other "C"-based systems with NO reason to post a BIOS data-table at 0:400! That is my guess re: what is occurr

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> 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

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

>> 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 inte

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

and their media-changes runs fine. As I want to keep UIDE/UIDE2 simple, I shall leave things 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 dis

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

s that are "seen" when VirtualBox runs are INCORRECT! > maybe the real issue is that noone finds the time to do a tiny bit of > debugging the problem but finds a lot of time to write loong > emails To which I shall add:

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

> 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 da

Re: [Freedos-user] Virtual floppy change problem and slow VirtualBox U IDE2 init problem

>> 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

Re: [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem

g 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 -- Live Sec

Re: [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem

n Why-in-HELL do you suggest any OTHER "possibilities", as in much of your comment above?? >> Also, better if you refer to "UIDE" in general... > > Honestly I am no expert in any UIDE* source, as things > are very packed and rank small size over easy to read &g

Re: [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem

-- 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 d

Re: [Freedos-user] Virtual floppy change problem and slow VirtualBox UIDE2 init problem

unnecessary busses/devices. In any case, no one has ever complained about the speed of UIDE's or UIDE2's initialzation, except when running "VirtualBox"! Also, better if you refer to "UIDE" in general,

Re: [Freedos-user] Virtual floppy change problem

Thanks to you, as well! 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 Exclusiv

Re: [Freedos-user] Virtual floppy change problem

>>>> -- UIDE2 has only 16 spare bytes before it goes back over a 7K >>>> .SYS file! But, I shall find a way! >>> >>> No doubt you will. >> >> In fact only 12 bytes, and I required only 11 of them for /N5, so >> UIDE2 still has 1 spare!

Re: [Freedos-user] Virtual floppy change problem

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,

[Freedos-user] New UIDE/UIDE2 With "VirtualBox" /N5 Switch.

Johnson Lam has posted a new 20-May-2012 DRIVERS.ZIP file with updated UIDE and UIDE2 drivers, on his website at: UIDE and UIDE2 now have a /N5 switch, to disable diskette caching when running with "VirtualBox" or other emulators which do NOT post a disk

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

(caching) 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 Exclu

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

it goes back over a 7K .SYS file! But, I shall find a way! 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

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

for UltraDMA I-O, which is "Better than nothing!" as we say, but absolutely NOT as fast as its caching routines! Jack R. Ellis -- Live Security Virtual Conference Exclusive live event will cover all the wa

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

; for you, if you must ever use multiple diskettes in VirtualBox with UIDE again, is to issue "CC" if your diskette must be changed. This will "flush" UIDE's cache and prevent the "same diskette" problem from occurring. Jack R. Ellis ---

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

that the writers of VirtualBox "Follow the RULES!" for PC hardware, instead of leaving you and I (perhaps others as well) to make changes in long-established programs just for them!! Jack R. Ellis -- Live Secu

Re: [Freedos-user] Virtual floppy change problem with VirtualBox

from about 1985 onward. I suggest you "Have 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

Re: [Freedos-user] sata drivers for cd, dvd, and hard disk

DROM.SYS or VIDE-CDD.SYS drivers. They do not provide CD/DVD caching (HUGE speed improvement!), nor do they use UltraDMA I-O, present in all CD/DVD drives from about 1999 onward. UIDE does both. Any questions re: UIDE usage/installation/etc., feel free to send me an E-Mail, and I shall be glad to help

Re: [Freedos-user] Freedos 1.1 install errors...

>>> ... With my own testing I found JEMMEX more compatible than XMGR >>> or HIMEMX + JEMM386 in various cases, but on other systems it is >>> different, as Mike mentioned ... >> >> To WHAT "incompatibilities" are you referring?? > > The A20 stuff that Syslinux/Isolinux (and MEMDISK) mess around wit

Re: [Freedos-user] Freedos 1.1 install errors...

> ... With my own testing I found JEMMEX more compatible than XMGR or > HIMEMX + JEMM386 in various cases, but on other systems it's different, > as Mike mentioned ... To WHAT "incompatibilities" are you referring?? Be advised of the following -- 1) JEMMEX/JEMM386 use "old" memory-test schemes,

Re: [Freedos-user] Long-term survival of FreeDOS

... Well, I would say "Saints be Praised"! Perhaps I am not the only one who regards AHCI as a big waste-of-time. Or money -- Is this new Intel chipset intended to be a "low cost" model? I will wait to see if Intel later r

Re: [Freedos-user] Long-term survival of FreeDOS

On Tue, 10 Apr 2012 22:16:50 -0700, Ralf A. Quint 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 start

Re: [Freedos-user] Freedos 1.1 install errors...

>> actually I would not even OFFER a boot menu item to skip loading the >> XMS driver at all: You cannot even boot the install CD / USB on old >> pre-XMS PC. > > Probably a bad idea for compatibility reasons, unless you offer multiple > choices for which XMS manager to install. E.g., I have a c

Re: [Freedos-user] Long-term survival of FreeDOS

> 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/DV

[Freedos-user] New 23-Mar-2012 UIDE/UIDE2 -- Minor SIze Reduction.

Johnson Lam has posted a new DRIVERS.ZIP file, now dated 23-Mar-2012, on his website at: 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, an

[Freedos-user] VERY Funny "Off Topic" --

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

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

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 h

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

ely, it seems that nobody listened. I did read Wirth's comments, and he is essentially correct, although he LOST my attention by making his project specific for his needs, e.g. it includes an object-oriented language (YECCH to me, even more than "C"). And I agree, nobody list

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

86 is NOT "solely" an "EMS" driver, not as it evolved. You are free to quote its extra features, like VCPI. I hope you see I am NOT-interested in VCPI, or DPMI, or anything but "regular" XMS, as that is the only system feature besides Int 13h on which my run-time driv

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

>> 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 U

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

>> 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 per

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

>> 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

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

> 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

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

> 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

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

>> 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

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

>> 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 ... JEMME

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

>> 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

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

dinary" word! >> Forgot to mention in my last post that if you do run >> UIDE2 in HMA space with /H, you must limit the cache [..] > > Thanks, I think, that it could be worthy to add this comment to > UIDE's readme.txt. I keep my README.TXT file small, as John

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

uot;Sorcerer"! > > "Wizard" is a better fit ;) - "Sorcerer" means the evil kind. Not always: King Arthur's "Merlin the Magician" is usually portrayed as a "Good Guy", and it is him I usually have in mind. If I want to be seen as a bit mor

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

s no FAT32 nor "long 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 Azu

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

rnel doesn't make HMA space available to drivers until AUTOEXEC is run, so you 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/ cachin

Re: [Freedos-user] zbigniew system stability with different shells, kernels and drivers

> 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,

Re: [Freedos-user] New 7-Mar-2012 UIDE, Etc. -- UIDE2 Under 7K!

IOSTAR main- board and 1-GB of RAM. Has run perfectly for 5 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:

Re: [Freedos-user] New 7-Mar-2012 UIDE, Etc. -- UIDE2 Under 7K!

u be more specific about how the driver "breaks"?? Does it display its "title" message and controller/device data, or does it simply crash?? Let me know. Jack R. Ellis -- Virtualization &

[Freedos-user] New 7-Mar-2012 UIDE, Etc. -- UIDE2 Under 7K!

Johnson Lam has posted a new 7-Mar-2012 DRIVERS.ZIP file with a much smaller UIDE2, on his website at: 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 t

Re: [Freedos-user] Problem after updating to FreeDOS 1.1 with writing of environment variables.

eliminates your "Ghost" problem, then (A) you need to disable the "Ghost" I-O logic and run your CD/DVD drives only 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 ha

Re: [Freedos-user] Problem after updating to FreeDOS 1.1 with writing of environment variables.

u may want to use BUFFERS=4, or at most BUFFERS=10, in your CONFIG.SYS file. WIth UIDE present, 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 &q

[Freedos-user] New UIDE -- Website Correction!

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 -- My apologies -- "Age 66 is SO much fun!" as I often say! ---

[Freedos-user] New UIDE Available -- "64K Boundaries" Fixed.

Johnson Lam has posted a new DRIVERS.ZIP dated 24-Feb-2012 on his website at . 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 d

[Freedos-user] UIDE Update Coming -- DISGUSTING Implications!!

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 "gener

Re: [Freedos-user] USB/ASPI to DOS, 4K sectors.

> 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 tru

Re: [Freedos-user] Re : Support for 4k byte sectors

> 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 >

Re: [Freedos-user] Re : Support for 4k byte sectors

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

Re: [Freedos-user] Re : Support for 4k byte sectors

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 physical

  1   2   3   >