[Freedos-user] Please remove me
Hi, As I will not have internet connection for 3 months, please remove me from both user and devel lists (don't want to fill up my mailbox). Best regards, Fox --- 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=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] NTFS4DOS and FreeDOS - Works with UMBPCI, Fails with EMM386
Hi! 11-Июл-2005 17:51 [EMAIL PROTECTED] (Michael Devore) wrote to freedos-user@lists.sourceforge.net: MD Never load a driver, shell, or application before HIMEM and EMM386. They MD are fundamental first loaders as they configure your basic memory MD situation. That SHELL command has got to come later in CONFIG.SYS. The MD rest should be fine, although I'd still stick them afterwards for form's MD sake. SHELL=a:\command.com /p 1234?DEVICE=A:\FDOS\HIMEM.EXE SHELL is parsed later than any DEVICE statement, together with INSTALL and SET. And it not changes anything, beside internal buffer, where remembered argument of this statement. --- 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_idt77alloc_id492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] More FreeDOS FDISK tests - failure is repeatable
At 03:29 PM 7/23/2005 +0100, Gerry Hickman wrote: Biggest mitigating factors are that if your hard drive behaves without errors, is reasonably standard with expected parameters, and there is no corruption of the program, the MBR write on startup won't occur. Ah, so this bug only happens with faulty hard-drives or file-systems? No, it also happens if there is a something which corrupts FDISK during runtime -- what that might be we don't know as yet, it could be FDISK itself or it could be something else. The problem can also happen if FDISK doesn't understand the BIOS information it receives. I do not know whether that situation actually occurs in real life systems. Beyond that, I could come up with other scenarios that might fail, but one could speculate for hours on any number of potential failure risks when using DOS and I don't think it would productive to do that. Basically, FDISK is currently operating with a big hole in the safety net users generally accept as being present. But as your disks are brand new without existing data, any overwrite of your disks' MBR with garbage would be a fairly minor nuisance, easily corrected by other means. --- 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=7477alloc_id=16492op=click ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
