VOGONS


Reply 40 of 45, by squeeb

User metadata
Rank Newbie
Rank
Newbie

Something worth mentioning here, CTMOUSE may only work with a USB mouse that supports the PS/2 protocol (ie one that can use those green adapters) on certain motherboards. I believe USB legacy mode in BIOS is supposed to cover this, but at least in my case (MSI K8MM-V), it did not. Cutemouse (even the newest version 2.1 beta 4) refused to work with my wired 'Classic IntelliMouse' (2017 model). I tried out an older Sony USB optical mouse I had laying around via PS/2 adapter, and sure enough it worked perfectly in DOS.

But still, fantastic guide Phil. I've been subbed to you for a while now on YouTube and your work is fantastic and provides an amazing resource for retro gaming on PC.

uz1jma-2.png

Reply 42 of 45, by Sjollico

User metadata
Rank Newbie
Rank
Newbie
ras2a wrote on 2020-06-25, 18:20:

Excellent stuff. Will I be able to install my ESS Audodrive ISA soundcard for use in DOS mode or would I require more steps?

I find ESS drivers even easier to install than the Creative drives. ESS cards also tend to have great compatibility with DOS games! Find the DOS drivers here http://vogonsdrivers.com/index.php?catid=17, move them to your retro PC and run the install in DOS and you are set to go!

Reply 43 of 45, by ras2a

User metadata
Rank Newbie
Rank
Newbie
Sjollico wrote on 2020-06-26, 17:40:
ras2a wrote on 2020-06-25, 18:20:

Excellent stuff. Will I be able to install my ESS Audodrive ISA soundcard for use in DOS mode or would I require more steps?

I find ESS drivers even easier to install than the Creative drives. ESS cards also tend to have great compatibility with DOS games! Find the DOS drivers here http://vogonsdrivers.com/index.php?catid=17, move them to your retro PC and run the install in DOS and you are set to go!

FANTASTIC! Thank you so much 😃

Reply 44 of 45, by NyLan

User metadata
Rank Newbie
Rank
Newbie

Hi,

I'm not sure to understand why, but I'm getting error messages when restarting ( and selecting choice 1 or 2, not tested others. )
ERROR: Unable to control A20 line !
XMS Driver not installed

and

Warning: the high memory area (HMA) is not available.
Additional low memory ( below 640k) will be used instead.

I also tested the file you provided on your other DOS Guide ( the pif itself ). I'm not getting an error message but I'm getting 494K of conv memory.

Seems I'm missing something.

Edit : Found the root cause, M=2 Argument saved me 😀

Last edited by NyLan on 2020-09-08, 12:43. Edited 1 time in total.

My Intel SE440BX-2 Intel's website Mirror : Modified to include docs, refs and BIOSes.

Reply 45 of 45, by amalgim

User metadata
Rank Newbie
Rank
Newbie
CrimsonMachete wrote on 2020-03-19, 03:39:
So, have run into a weird problem. […]
Show full quote

So, have run into a weird problem.

Followed the very useful guide above last night, had my AWE64 working perfectly in MS-DOS mode on my P2 system, but after returning to Windows and back to DOS all my settings reverted and my autoexec and config were made into .bak files, long story short but when trying to fix that I borked my install with a reboot loop and decided to start from scratch.

This time round when trying to use SETVER command on the DOS installation files have been running into trouble; first it says DEVICE=C:\WINDOWS\SETVER.EXE in the CONFIG.SYS from the Exit to Dos.pif is missing, when it isn't. Using Phil's standalone restart_in_msdos.pif the SETVER command now works, however when running the Install.exe from sbbasic I for some reason DON'T get the script error code (which I got yesterday), and the install won't progress past the next screen.

Sorry about the wall of text, but any ideas what might be going wrong here? I'm not understanding why the SETVER command isn't working with the Exit to Dos.pif when it clearly (I think) should be. Getting frustrated here, probably going to have to start from scratch again.

I had this same issue. Replace the device=c:\windows\setver.exe with devicehigh=c:\windows\setver.exe and it should work now (or at least it did for me)