[Freedos-user] For Eric - NWCACHE write caching test results; and a new problem

2006-08-31 Thread saywhat
There's good news and there's bad news. The good news is that, as you expected, there's only a small difference between a big write cache with a long delay and a small write cache with a short delay. The bad news is that I found some big performance problems (in reading and

[Freedos-user] Results of SMARTDRV directory corruption tests

2006-08-27 Thread saywhat
Here is what I've found: 1) The error is repeatable. I used UKA17X2.EXE to produce this error over and over again. UKA17X2 creates ~300 files. Other pgms that create a lot of files could probably be used just as well. Here is the sequence that I used to reproduce the error:

Re: [Freedos-user] Results of testing fdbasecd.iso dated...

2006-08-22 Thread saywhat
Arkady V.Belousov writes: 21-???-2006 14:07 [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote to snI will ask this question: If FreeDOS is released as is, and users sn start seeing these msgs on their PCs, will they know that the problem sn is *not* caused by FreeDOS? So, you think,

Re: [Freedos-user] corrupted directory sector from using SMARTDRV 6.22 with FreeDOS?

2006-08-22 Thread saywhat
Michael Devore wrote: At 02:50 PM 8/21/2006 -0600, Eddie wrote: I was really hoping that this problem had been silently fixed by all of the other work that has been done recently. Doesn't look VDS-related, the executable only uses a couple of common calls there. Not much more I can

Re: [Freedos-user] Results of testing fdbasecd.iso dated...

2006-08-22 Thread saywhat
Blair Campbell wrote: Those are more likely ISOLinux issues, and most users will probably not be using PART (which seems to interpret ISOLinux somehow as a virus, which would somewhat seem like a PART bug to me at least). I figured that ISOLinux might be the culprit since PART was

[Freedos-user] corrupted directory sector from using SMARTDRV 6.22 with FreeDOS?

2006-08-21 Thread saywhat
This problem occurs when using SMARTDRV.EXE (with write caching enabled) from MSDOS 6.22 with FreeDOS. Replacing either avoids the problem. I haven't pinned it down yet but the problem seems to occur with more than just one pgm. I've seen it when installing UKA17X2 (i.e. UKA_PPP),

Re: [Freedos-user] Results of testing fdbasecd.iso dated...

2006-08-21 Thread saywhat
Arkady V.Belousov wrote to freedos-user@lists.sourceforge.net: sn h) Boot from first harddisk (0x80) sn I fell into this because of the timeout. The next two lines on the sn screen are: sn Booting from local disk... sn Virus!!! This may be message from BIOS (if there is turned on

[Freedos-user] Results of testing fdbasecd.iso dated 08/19/2006, pt.2

2006-08-20 Thread saywhat
Continuing on the escape menu This menu is apparently inevitable. The installation process shows this menu regardless of what you choose on the preceding menu. E.g. after the previous tests, I created and formatted a new ~120MB partition just for FreeDOS. Then I rebooted from the

[Freedos-user] Results of testing fdbasecd.iso dated 08/19/2006

2006-08-19 Thread saywhat
Test environment .486DX4-100 w/32MB RAM .ATAPI cdrom drive .500MB hdd (with ~120MB of unused (no partition defined there) space) .The hdd also contains 2 ~60MB primary partitions and a ~250MB extended partition (which contains a few more (logical) partitions). All