DOS ain't dead

"Be Advised ..." About Using UIDE! (Users)

posted by Jack , Fresno, California USA, 24.05.2010, 16:18

> I have to remark that it is no offense to Jack and his UIDE. I know that
> he always tests his software very detail so it is unlikely that it is the
> cause. Anyway - do you have any suggestions? Should I use another
> kernel? Should I again run UIDE without /P? Something else?

"Be advised" these two things about UIDE. First, UIDE has absolutely NO
logic related to DOS directories or file structures. It reads or writes
data ONLY "to order" of the DOS system and then ONLY using a 24-bit "CHS"
address (V6.22 MS-DOS and older) or a 48-bit "LBA" address (V7.10 MS-DOS,
Win95/98, etc.). That is all UIDE gets from the system, when it gets an
"Int 13h" request to do disk I-O. Thus, if your directories or data get
corrupted, blame the "Commanding General" and not the poor-old "private",
and look at what disk orders the DOS system is "sending down" to UIDE!

Second, as I note in the README for my drivers, MS-DOS systems have a LOT
of ancient and uncorrected PROBLEMS in declaring "free" HMA space. With
V6.22 MS-DOS that I still have, it "declares" 26K of available HMA, but I
dare NOT take over 19K for UIDE's binary-search table, or the system will
CRASH sooner-or-later! V7.10 MS-DOS has a lot LESS -- It "declares" 13K
of available HMA, but UIDE dare not take over 9136 bytes, as I discovered
3 years ago!

I know FreeDOS is not MS-DOS, but if its HMA logic was based on that used
by MS-DOS, the same problems could exist!! Thus, you should try running
UIDE with /P (faster speed) but WITHOUT an /HL or /H switch (use no HMA).
This will require a bit more upper-memory, about 20K with a 500-MB cache.

However, if loading UIDE only in upper-memory (no /H nor /HL) avoids your
disk corruption, then FreeDOS must ALSO have problems in declaring "free"
HMA space! You then have two choices: Run UIDE with /P but without /HL
or /H and "tolerate" its using extra upper-memory; or run UIDE without /P
which takes a maximum 3840 bytes of HMA space and should not "bother" any
DOS system, even those with HMA-reporting errors! Not using /P will run
a bit slower, I know, but it may be necessary to solve your problems.

If NONE of these ideas about UIDE help, then "You know who to call!" i.e.
speak to the Volkov or FreeDOS people instead!

---
(Account disabled on user's request.)

Complete thread:

• What can cause FAT damage - kernel 2039 or UIDE? - Laaca, 24.05.2010, 08:50 (Users)
  • BUG #2901916 | can cause FAT damage - kernel 2039 or UIDE? - DOS386, 24.05.2010, 09:20
  • What can cause FAT damage - kernel 2039 or UIDE? - Khusraw, 24.05.2010, 13:26
    • Buggy FreeDOS - DOS386, 06.06.2010, 15:59
      • Buggy FreeDOS - Laaca, 06.06.2010, 17:19
      • Buggy FreeDOS - Khusraw, 06.06.2010, 17:49
  • "Be Advised ..." About Using UIDE! - Jack, 24.05.2010, 16:18
    • "Be Advised ..." About Using UIDE! - Khusraw, 24.05.2010, 16:57
      • "Be Advised ..." About Using UIDE! - Jack, 24.05.2010, 17:21
        • "Be Advised ..." About Using UIDE! - Laaca, 24.05.2010, 18:15
          • "Be Advised ..." About Using UIDE! - Khusraw, 24.05.2010, 18:59
            • For the dummies - Khusraw, 24.05.2010, 19:28
              • For the dummies - Laaca, 24.05.2010, 21:07
                • For the dummies - Khusraw, 24.05.2010, 22:18
              • .. - DOS386, 03.05.2011, 09:43
          • You May Need "V8.0" MS-DOS! - Jack, 24.05.2010, 19:09
            • May Need "V8.0" MS-DOS! Or NOT ! - Ninho, 25.05.2010, 12:27
              • Deep directories in DOS - jassenna, 27.05.2010, 06:45
                • Deep directories in DOS - Ninho, 30.05.2010, 12:38