Can you duplicate the problem with the latest Windows version of DOSBox? Also, did you set up this Windows 3.1 installation yourself? (What is windows.bat ?)

I don't think anyone has mentioned using 1MBFort here before.

Jorpho wrote:

Can you duplicate the problem with the latest Windows version of DOSBox? Also, did you set up this Windows 3.1 installation yourself? (What is windows.bat ?)

I don't think anyone has mentioned using 1MBFort here before.

Thx for the quick response.

Yeah I searched out 1MBFort. Didn't see it mentioned here.

I did the installation myself a while back. But, my file structure is the same/similar as the thread I was viewing on the same topic I was using in an attempt to solve my issue earlier.

1# Lines in this section will be run at startup.
2# You can put your MOUNT lines here.
3
4imgmount d /home/pi/RetroPie/roms/pc/Civilization2/Civ2.cue -t iso -fs iso
5mount c /home/pi/RetroPie/roms/pc/Windows3.1/
6C:
7cd windows 
8win c:\windows\runexit d:\Civ2\Civ2.exe
9exit

Still no go. This command doesn't auto exe Civ2 and also gives me the insufficient memory when I open it manually.

Not sure if this is at all helpful, but with MSDogs:

1win d:\DOGS.EXE

works, but

1win c:\windows\runexit d:\DOGS.EXE

gives me an error "Application Error Exception EGPFault in module SB16SND.drv at 0001:3193. General protection fault in module SB16SND.drv at 0001:3193." Do I have too many active drivers? Any way to check that out?

Here is my System.INI

1[boot]
2386grabber=VGA_ENG.3GR
3oemfonts.fon=8514OEM.FON
4fixedfon.fon=8514FIX.FON
5fonts.fon=8514SYS.FON
6display.drv=S3TRIO.DRV
7shell=progman.exe
8network.drv=
9mouse.drv=mouse.drv
10language.dll=
11sound.drv=mmsound.drv
12comm.drv=comm.drv
13keyboard.drv=keyboard.drv
14system.drv=syshook.drv 
15drivers=mmsystem.dll winmm16.dll msmixmgr.dll
16SCRNSAVE.EXE=C:\WINDOWS\DOGBOD16.SCR
17
18[keyboard]
19subtype=
20type=4
21keyboard.dll=
22oemansi.bin=
23
24[boot.description]
25aspect=100,120,120
26display.drv=S3 Trio64V 1.69.02 1024x768 256 C LF
27keyboard.typ=Enhanced 101 or 102 key US and Non US keyboards
28mouse.drv=Microsoft, or IBM PS/2
29language.dll=English (American)
30system.drv=MS-DOS System
31codepage=437
32woafont.fon=English (437)
33network.drv=No Network Installed
34secondnet.drv=No Additional Network Installed
35
36[386Enh]
37device=dva.386
38DMABufferSize=64
39MaxBPs=768
40display=VDDS3764.386
41EGA80WOA.FON=EGA80WOA.FON
42EGA40WOA.FON=EGA40WOA.FON
43CGA80WOA.FON=CGA80WOA.FON
44CGA40WOA.FON=CGA40WOA.FON
45device=C:\WINDOWS\SYSTEM\windpmi.386
46device=C:\WINDOWS\SYSTEM\WIN32S\W32S.386
47mouse=*vmd
48ebios=*ebios
49woafont=dosapp.fon
50device=*vpd
51keyboard=*vkd
52network=*dosnet,*vnetbios
53netheapsize=16
54device=*vcd
55device=*vpicd
56device=*vtd
57device=*reboot
58device=*vdmad
59device=*vsd
60device=*v86mmgr

61device=*pageswap
62device=*dosmgr
63device=*vmpoll
64device=*wshell
65device=*PAGEFILE
66device=*BLOCKDEV
67device=*vfd
68device=*parity
69device=*biosxlat
70device=*vmcpd
71device=*combuff
72device=*cdpscsi
73device=vtdapi.386
74device=vpmtd.386
75device=vcomm.386
76device=serial.386
77device=lpt.386
78device=ifsmgr.386
79device=vcache.386
80device=vshare.386
81local=CON
82FileSysChange=off
83COM3Irq=4
84COM3Base=03E8
85COM4Irq=3
86COM4Base=02E8
87PagingFile=C:\WINDOWS\WIN386.SWP
88MaxPagingFileSize=61440
89SysVMIn2ndBank=FALSE
90device=vsbpd.386
91MinTimeslice=1
92WinTimeslice=100,50
93WinExclusive=0
94Com1AutoAssign=2
95Com2AutoAssign=2
96LPT1AutoAssign=60
97LocalLoadHigh=Off
98RMMTimeout=500
99lowreservoir=500
100
101[NonWindowsApp]
102localtsrs=dosedit,ced
103
104[vcache]
105minfilecache=512
106
107[mci]
108WaveAudio=mciwave.drv
109Sequencer=mciseq.drv
110CDAudio=mcicda.drv
111AVIVideo=mciavi.drv
112QTWVideo=C:\WINDOWS\SYSTEM\MCIQTW.DRV
113
114[drivers]
115timer=timer.drv
116midimapper=midimap.drv
117VIDC.IV41=ir41.dll
118VIDC.IV32=ir32.dll
119VIDC.IV31=ir32.dll
120VIDC.YVU9=iyvu9.dll
121VIDC.CVID=iccvid.drv
122VIDC.MSVC=msvidc.drv
123VIDC.MRLE=msrle.drv
124WaveMapper=msacm.drv
125MSACM.msadpcm=msadpcm.acm
126MSACM.imaadpcm=imaadpcm.acm
127Midi=sb16fm.drv
128Midi1=sb16snd.drv
129Wave=sb16snd.drv
130Aux=sb16snd.drv
131Mixer=sb16snd.drv
132joystick=ibmjoy.drv
133VIDS.DRAW=UDH.DLL
134DCI=RFMDCI
135
136[DDEShares]
137CHAT$=winchat,chat,,31,,0,,0,0,0
138SCHAT$=winchat,chat,,31,,0,,0,0,0
139CLPBK$=clipsrv,system,,31,,0,,0,0,0
140HEARTS$=mshearts,hearts,,15,,0,,0,0,0
141
142[Network]
143winnet=nonet
144multinet=nonet
145FileSharing=No
146PrintSharing=No
147
148
149[svga256.drv]
150resolution=2
151dpi=96
152
153[network drivers]
154devdir=C:\WINDOWS
155LoadRMDrivers=No
156[sndblst.drv]
157Port=220
158Int=7
159DmaChannel=1
160MidiPort=330
161HDmaChannel=5
162FDMAPlayBack=1
163FDMARecording=1
164FullDuplex=1
165VoiceVolume=16, 16
166FMVolume=16, 16
167CDVolume=16, 16
168LineVolume=16, 16
169MicVolume=16
170MasterVolume=16, 16
171SpeakerVolume=16
172AuxVolume=0, 0
173InputMasterVolume=16, 16
174MuteVirtual=10
175OutputMixerSwitch=6
176BassTone=16, 16
177TrebleTone=16, 16
178RecordGain=1, 1
179OutputGain=1, 1
180AGC=0
181Mux_WaveIn=1e
182SaveOnExit=0
183
184[Debug]
185OutputTo=NUL
186
187[DISPLAY]
188decimation=3000
189dac-type=nbt
190polygon-support=on
191ellipse-support=on
192scache=on
193textrmw=0
194fastmmio=on
195screen-size=1024
196color-format=8
197dpi=120
198
199[ibmjoy.drv]
200Axes=2
201
202[mciseq.drv]
203disablewarning=true
204
205[msacm.imaadpcm]
206MaxRTEncodeSetting=6
207MaxRTDecodeSetting=6
208
209[msacm.drv]
210Playback=SB16 Wave Out [220]
211Record=SB16 Wave In [220]
212PreferredOnly=1
213

So, in regards to my other question:

hooperre wrote:

When I boot up Windows 3.11 by calling windows.bat I can manually run Civ2.exe with no issues.

What is windows.bat ? This would seem to be rather crucial in solving the problem.

Jorpho wrote:

So, in regards to my other question:

hooperre wrote:

When I boot up Windows 3.11 by calling windows.bat I can manually run Civ2.exe with no issues.

What is windows.bat ? This would seem to be rather crucial in solving the problem.

Ah sorry. It's a batch file in my virtual C: folder. I read it was necessary for sound blaster drivers.

1@c:\windows\smartdrv.exe
2@SET PATH=%PATH%;C:\WINDOWS; 
3@SET TEMP=C:\WINDOWS\TEMP
4@lh devlod C:\SB16\DRV\CSP.SYS /UNIT=0 /BLASTER=A:220
5@lh devlod C:\SB16\DRV\CTMMSYS.SYS
6@SET SOUND=C:\SB16
7@SET BLASTER=A220 I7 D1 H5 P330 T6
8@SET MIDI=SYNTH:1 MAP:E
9@C:\SB16\MIXERSET /P /Q
10@windows\win /b

I followed a tutorial elsewhere and I think I installed the wrong SB drivers or something. Any idea how to remove them and replace them with the drivers in the guide thread?

None of the entries of this batch file are needed for Windows 3.x (nor are any of the devices you load necessary for Dosbox).

Why have a batch file in the Windows directory to start Windows when you could simply use "WIN.COM" in Windows?

collector wrote:

Why have a batch file in the Windows directory to start Windows when you could simply use "WIN.COM" in Windows?

If I use win.com without the batch file I get the memory error.

1imgmount d /home/pi/RetroPie/roms/pc/Civilization2/Civ2.cue -t iso -fs iso
2mount c /home/pi/RetroPie/roms/pc/Windows3.1/
3C:
4civ2.bat
5exit

Created a Civ2 batch file

1@c:\windows\smartdrv.exe
2@SET PATH=%PATH%;C:\WINDOWS; 
3@SET TEMP=C:\WINDOWS\TEMP
4@lh devlod C:\SB16\DRV\CSP.SYS /UNIT=0 /BLASTER=A:220
5@lh devlod C:\SB16\DRV\CTMMSYS.SYS
6@SET SOUND=C:\SB16
7@SET BLASTER=A220 I7 D1 H5 P330 T6
8@SET MIDI=SYNTH:1 MAP:E
9@C:\SB16\MIXERSET /P /Q
10@windows\win d:\civ2\civ2.exe /b

This launches the game on start up without the memory error. I don't know I'm baffled.

If I use runexit.exe before the civ2 call it won't open.

Well, standard troubleshooting at this point would be to take lines out of that batch file one by one and see if you can isolate whatever is magically allowing Civ2 to run. I would start by seeing if the environment variables alone (i.e. everything that starts with "SET") are enough. But as Mr. Dominus suggested, none of those lines ought to be necessary, as DOSBox simply doesn't work that way.

Jorpho wrote:

Well, standard troubleshooting at this point would be to take lines out of that batch file one by one and see if you can isolate whatever is magically allowing Civ2 to run. I would start by seeing if the environment variables alone (i.e. everything that starts with "SET") are enough. But as Mr. Dominus suggested, none of those lines ought to be necessary, as DOSBox simply doesn't work that way.

1@c:\windows\smartdrv.exe
2@lh devlod C:\SB16\DRV\CTMMSYS.SYS
3@windows\win windows\runexit  d:\civ2\civ2.exe

Launches runexit version of Civ 2 but get an error:
Error "+8" in module 4
File open failed: Modules.db
Most recent dos error: 2

If I remove runexit it runs fine.

Smartdrv does nothing in Dosbox.

Drop all of the memory management and driver loading stuff.

collector wrote:

Drop all of the memory management and driver loading stuff.

Appreciate y'all sticking with me so far as I know this is a weird snafu I'm dealing with. I can't find the source that told me to build this batch file and install those drivers. Hope you find this interesting if nothing else...

1@c:\windows\smartdrv.exe
2@lh devlod C:\SB16\DRV\CTMMSYS.SYS
3@windows\win d:\civ2\civ2.exe

This is the minimum I can call without getting the memory error. The first two lines seem necessary for some reason.

1@windows\win d:\civ2\civ2.exe

This will yield a memory error if I open any program including FileManager or WinSetup. I feel like if I could just uninstall the soundblaster drivers and install the ones listed in y'all's setup guide maybe I would get somewhere with this, but of course it's not that straight forward with Win3.11. I tried a straight install of your drivers on top of mine and nothing came of it.

I don't know what guide you followed when you made this installation in the first place, but I can't recall anyone mentioning problems like this after following the "Win3.11 in DOSBox" guide on these forums. Maybe starting over from scratch would be the best idea.

(If that sounds like too much trouble, then someone out there probably has a pre-constructed DOSBox+Win3.11 setup – but of course you use such things at your own risk.)

The only other thing I might suggest at this point is changing the "cpu_type" in DOSBox.conf to 486_slow, but that shouldn't be necessary either.

Jorpho wrote:

I don't know what guide you followed when you made this installation in the first place, but I can't recall anyone mentioning problems like this after following the "Win3.11 in DOSBox" guide on these forums. Maybe starting over from scratch would be the best idea.

(If that sounds like too much trouble, then someone out there probably has a pre-constructed DOSBox+Win3.11 setup – but of course you use such things at your own risk.)

The only other thing I might suggest at this point is changing the "cpu_type" in DOSBox.conf to 486_slow, but that shouldn't be necessary either.

Yeah, thanks. I didn't know y'all's guide existed, I think I just used some cockamamie YouTube tutorial and now I don't have access to a floppy drive anymore. Since then, I've gotten significantly better with DOSBox so I probably could have navigated it myself. Oh well. Best thing to do at this point may be using batch files for all files I want to call immediately from EmulationStation.