MAMEWorld >> EmuChat
View all threads Index   Threaded Mode Threaded  

Pages: 1

BIOS-D
MAME Fan
Reged: 08/07/06
Posts: 1688
Send PM


at486 and Win 3.1x... maybe I'm doing something wrong?
#347158 - 11/19/15 01:50 AM


I tried to run some old DOS games full screen on MAME without the bother of VMWare not able to lock mouse cursor or that bar at the bottom when full screen. Most games run fine so then I moved to the next step: Windows. Windows 95 installs fine. There was a weird video glitch when colors set to 256 colors, but it got fixed when I installed DirectX. I tried also every Windows 3.1x available (even 'for Workgroups'), but it hangs right at the 2nd/3rd disk (when it finishes copying files and ask you to wait a while). I've played with many basic slot devices without success and I get the same result with at386 and ct486.

I run driver using this:

mame64.exe at486 -harddisk at486_C1015_H16_S63.chd -ramsize 16m

DOS version is 6.22 with MSCDEX installed.

I also tried imgtool to inject files into blank disks (so I don't burn files into ISO images to copy them) but I can't even create them. It hangs on this command.

imgtool.exe create fdi_fat test.fdi

I know the driver is set as "Not working", but I remember I could run Win 3.1 before. Maybe I am missing something else.



Haze
Reged: 09/23/03
Posts: 5245
Send PM


Re: at486 and Win 3.1x... maybe I'm doing something wrong? new [Re: BIOS-D]
#347162 - 11/19/15 03:03 AM


I seem to remember it not liking whatever the default mouse type is in the driver unless you specifically load a compatible mouse driver first (the detect code causes the machine to hang)

MAME treats the mouse as a pluggable device, so you can specify a different type on the commandline. For some reason MAME also defaults to having 2 mice plugged in which might cause an issue as well

mame64 at486 -board2:comat:serport0 "msystems_mouse" -board2:comat:serport1 ""

tells it to just use the one mouse, plugged into serial port 0, with serial port 1 left empty...

you might still need to find a mouse driver to load tho.



> I tried to run some old DOS games full screen on MAME without the bother of VMWare
> not able to lock mouse cursor or that bar at the bottom when full screen. Most games
> run fine so then I moved to the next step: Windows. Windows 95 installs fine. There
> was a weird video glitch when colors set to 256 colors, but it got fixed when I
> installed DirectX. I tried also every Windows 3.1x available (even 'for Workgroups'),
> but it hangs right at the 2nd/3rd disk (when it finishes copying files and ask you to
> wait a while). I've played with many basic slot devices without success and I get the
> same result with at386 and ct486.
>
> I run driver using this:
>
> mame64.exe at486 -harddisk at486_C1015_H16_S63.chd -ramsize 16m
>
> DOS version is 6.22 with MSCDEX installed.
>
> I also tried imgtool to inject files into blank disks (so I don't burn files into ISO
> images to copy them) but I can't even create them. It hangs on this command.
>
> imgtool.exe create fdi_fat test.fdi
>
> I know the driver is set as "Not working", but I remember I could run Win 3.1 before.
> Maybe I am missing something else.

Edited by Haze (11/19/15 03:06 AM)



BIOS-D
MAME Fan
Reged: 08/07/06
Posts: 1688
Send PM


Re: at486 and Win 3.1x... maybe I'm doing something wrong? new [Re: Haze]
#347174 - 11/19/15 10:06 AM


Indeed, removing the mouse did the trick. I set no mouse, install, set default mouse back then install driver through setup.exe. Windows 3.1 is working good again. Thank you.


Pages: 1

MAMEWorld >> EmuChat
View all threads Index   Threaded Mode Threaded  

Extra information Permissions
Moderator:  Robbbert, Tafoid 
1 registered and 503 anonymous users are browsing this forum.
You cannot start new topics
You cannot reply to topics
HTML is enabled
UBBCode is enabled
Thread views: 1641