🚀 go-pugleaf

In article <1993Jan4.173117.14082@dcatlas.dot.gov>, joet@dcatlas.dot.gov (Joe Trott) writes:
> linstee@dutecaj.et.tudelft.nl (Erik van Linstee) writes:
> >The funniest thing happened to me. Yesterday, when I booted my
> >dos partition, I noticed I had no UMB's. I was rather surprised,
> >since I hadn't changed anything since I last used dos.
> >And behold, the himem.sys and emm386.exe settings were still
> >ok, yet, from the dos prompt (4dos or command.com) I could not
> >see any UMB's, emm386 repports 0 bytes available/free UMB
> >but a correct UMB start segment (C800), SI repports no UMB server
> >present, BUT the drivers in DEVICEHIGH's were loaded high and
> >functioning!!!
> 
> Are you sure they were up high?
> Sounds like some of your BIOS settings may have been changed, such as the ones
> for shadow RAM.  How much RAM is in your system?


Actually I've had UMB's disappear from MEM command's output,
however they were still there (of course). I haven't yet
been able to find the source of the problem,  but it looks
very much like a bug in DOS 5. 

I may not know exactly where the bug is coming from,  but it's
not in configuration or anything like that. My bet is that
DOS overwrites it's pointer to the first UMB.  When it looses
that,  the whole thing is gone as far as DOS knows. Naturally
the blocks remain there set up correctly and device drivers
still work correctly with pointers being bueno all around.

I suggest someone at Microsoft run DOS apps with debugging
set to the memory location of the UMB pointer...

Aki. 
-- 
/  Phone: 408-662 9664   Fax: 662 9676  |  586 is a 586 no matter what  \ 
\  125 Searidge Ct #D, Aptos, CA 95003  |  Intel seez.  "Pent... WHAT?" /