At 08:53 PM 8/8/2005 +0200, Bernd Blaauw wrote:
MS HIMEM (+FreeDOS EMM386.EXE) hardly takes any XMS.
EMM386 takes 223KB of XMS.
Takes UMBs from extended memory as well as DMA area and miscellany. As
would be expected.
---
SF.Net email
> I'm curious about this, "DOS-Compatible" means "SoundBlaster compatible
> API"?
I mean PCI cards that do not natively support DOS but will with
available drivers (distributable or non-distributable, they can be
downloaded for the user if they are non-distributable).
---
Conventional 640K18K 622K
Upper 128K10K 118K
Reserved 256K 256K 0K
Extended (XMS) 3,328K 1,000K 2,328K
Total memory4,352K 1,284K 3,068K
Lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- - OpenGEM Release 4 Update 4 now available (9/8/05)
OpenGEM Core, Complete and Experimental have now been updated. OpenGEM
Release 4 Update 4 patches are available from
http://gem.shaneland.co.uk/updates.html, and you can download the full
versions
Gerry Hickman wrote:
Hi Bernd,
...
*kernel 2034, 2035, 2035A and the CVS kernel
Sorry, I don't understnad. It looks like four different files (?) and I
can't work out how these numbers relate to the directory listing on the
fdos.org/kernel website.
4 different versions,
2034, 2035, and 20
Hi there,
Blair Campbell escribió:
Hi. I am reqesting that everyone with a PCI audio card that needs
DOS-compatible drivers to run and has those DOS-compatible drivers
available to send me the PCIsleep output for "pcisleep /q0401". This
will help me to add PCI audio card detection to my ISOs a
Similar to the request concerning PCI audio cards, I would also
appreciate anyone who can send me the PCIsleep /l output of cards that
work well with Scitech's UNIVBE
(http://www.scitechsoft.com/products/ent/free_titles.html) or with
other downloadable drivers. The same goes for DOS compatible PCI
Hi. I am reqesting that everyone with a PCI audio card that needs
DOS-compatible drivers to run and has those DOS-compatible drivers
available to send me the PCIsleep output for "pcisleep /q0401". This
will help me to add PCI audio card detection to my ISOs and make the
installation of FreeDOS ev
Bernd Blaauw wrote:
just copy IO.SYS, MSDOS.SYS and COMMAND.COM to C:,
then do SYS A: C: /BOOTONLY /OEM:MS
and reboot system.
Then check if MSDOS boots first, and only when it does,
install Windows.
I ran a similar test today, and got an unexpected result.
Using standard FreeDOS:
1. Booted u
Same happened to me last night too...
Glad to read this, I am becoming an anti-spam paranoid...
Aitor
Gerry Hickman escribió:
Hi,
Since this Saturday, my posts are not showing up on this list until I
re-post them about three times? There's no bounce message, they just
disappear...
--
Hi,
Since this Saturday, my posts are not showing up on this list until I
re-post them about three times? There's no bounce message, they just
disappear...
--
Gerry Hickman (London UK)
---
SF.Net email is Sponsored by the Better Software C
Hi Bernd,
just get the 'unofficial'/'development' versions of components.
*SYS 3.6 from www.fdos.org/kernel (sys.dev.com)
OK, I got this one from the hyperlink on the front page.
*kernel 2034, 2035, 2035A and the CVS kernel
Sorry, I don't understnad. It looks like four different files (?)
Bernd Blaauw wrote:
just copy IO.SYS, MSDOS.SYS and COMMAND.COM to C:,
then do SYS A: C: /BOOTONLY /OEM:MS
and reboot system.
Then check if MSDOS boots first, and only when it does,
install Windows.
I ran a similar test today, and got an unexpected result.
Using standard FreeDOS:
1. Booted u
Hi Bernd,
I've printed this out, I think I understand the important points and I'm
happy to run some tests, but can you clarify the exact files I need to
download. I currently have the latest "stable" kernel, command, and sys
files. My kernel says it's 1.1.35 and my sys says it's v3.2 - I want
Hi,
Since this Saturday, my posts are not showing up on this list until I
re-post them about three times? There's no bounce message, they just
disappear...
--
Gerry Hickman (London UK)
---
SF.Net email is Sponsored by the Better Software Con
Hi folks,
This is probably off-topic, so please ignore with my apologies.
There's a screenshot of guide at
http://www.anchor92.freeserve.co.uk/guide.htm .
Guide is a 32-bit multitasking operating system I've been developing, an
acronym for graphical user interface desktop environment. It run
This time, I still get TWO items on the Windows NT/2000 boot loader menu
1. Windows 2000
2. MS-DOS (as opposed to "Previous Operating System on C:")
I can confirm this: strangely upgrading from DOS 6.22, Win2000setup
doesn't finish and I get a spontaneous reboot during last phase of setup.
Bernd Blaauw wrote:
just copy IO.SYS, MSDOS.SYS and COMMAND.COM to C:,
then do SYS A: C: /BOOTONLY /OEM:MS
and reboot system.
Then check if MSDOS boots first, and only when it does,
install Windows.
I ran a similar test today, and got an unexpected result.
Using standard FreeDOS:
1. Booted u
18 matches
Mail list logo
