 |
|
boolybooly
|
|
it just wont run like that for me, maybe its my 1024 Mb RAM messing it up again, or perhaps my AMD Barton.
it wont run past game setup even using DOSbox 6.
|
|
|  |
 |
|
boolybooly
|
|
I have the game from 2 sources, one is moo_all from J Sullivan, which runs ok on a p3 in WinME and is v1.3.
the other is a dl, self installer, from gamebird.dk also 1.3
edit/ ahem! this morning they will both run in dosbox, as I set Win95 emulation on the dosbox exe. but in dosbox it will not load saved games at the moment, so it is not ideal.
in my version of XP pro sp1 both versions say that
"you must have at least 1024k of expanded memory" in the dos window after running orion.exe (if I uncheck the close window option in the shortcut otherwise it just blinks on then off)
also the instal exe reports that I have no EMS driver after soundcard setup.
I have tried running in Win95 emulation mode, with 1024 EMS specified in the shortcut and it makes no difference. in fact I have tried several tens of permutations of the memory settings.
maybe I should try a different version, vmxa1 your offer of a zip sounds good, if its not too much trouble, but I bet you it will do the same ! 
Last edited by boolybooly on 23-01-2004 at 14:11
|
|
|  |
 |
|
boolybooly
|
|
I am beginning to wonder if it is a bios level problem, this is an nForce2 mobo running DDR in dual channel mode and I wonder if it is bypassing elements of RAM control which still apply to my p3 rig as it has SDRAM. I will experiment with single channel mode.
I have tried running MoO from a WinME boot disk DOS prompt to its directory and I still get the "1024 expanded" error message.
I wonder what chipset Garth's rig uses ?
|
|
|  |
 |
|
boolybooly
|
|
Thanks vmxa1, I unzipped and placed MPS\Orion in C: then (presuming that is all I have to do) as a test I ran the orion.exe and the shortcut without any further tweaks and still get exactly the same message that I need 1024 of EMS.
So that means my system is not providing EMS support properly. It was a fresh instal on a blank C: Any ideas ?
|
|
|  |
 |
|
boolybooly
|
|
I tried with no startup items and all win.ini and system.ini boxes checked, every single service checked and dt@16bit. Orion.exe produced exactly the same message about needing EMS.
I dont understand why I am not getting EMS or rather why MoO is not seeing EMS even when I manually specify EMS 1024 and Win95 emulation in the shortcut.
I have one folder with the autoexec and config files & shortcuts set up and in that one I tried a config.nt line calling EMM386.exe which I placed in windows root, currently it contains the following.
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=40
device=%SystemRoot%\emm386 RAM
and the shortcut is using this config file as it recognises when it has bad syntax in it, i just dont know if this works with XP *shrug* worth a try
I also changed memory settings and noticed that the Total memory always resets to auto when I close the shortcut properties, ie if I set it to 640 manually it wont stick so I get the feeling XP is ignoring me.
|
|
|  |
 |
|
vmxa1
|
 |
Oviedo, Fl
Nov 2001 time: 21:33
|
|
I use auto for all of the mem settings.
Here is mine that I usd for MoM
REM Windows MS-DOS Startup File
REM ECHOCONFIG
REM NTCMDPROMPT
REM When you return to the command prompt from a TSR or while running an
REM MS-DOS-based application, Windows runs COMMAND.COM. This allows the
REM TSR to remain active. To run CMD.EXE, the Windows command prompt,
REM rather than COMMAND.COM, add the command ntcmdprompt to CONFIG.NT or
REM other startup file.
REM
REM DOSONLY
REM By default, you can start any type of application when running
REM COMMAND.COM. If you start an application other than an MS-DOS-based
REM application, any running TSR may be disrupted. To ensure that only
REM MS-DOS-based applications can be started, add the command dosonly to
REM CONFIG.NT or other startup file.
REM
REM EMM
REM You can use EMM command line to configure EMM(Expanded Memory Manager).
REM The syntax is:
REM
REM EMM = [A=AltRegSets] [B=BaseSegment] [RAM]
REM
REM AltRegSets
REM specifies the total Alternative Mapping Register Sets you
REM want the system to support. 1 <= AltRegSets <= 255. The
REM default value is 8.
REM BaseSegment
REM specifies the starting segment address in the Dos conventional
REM memory you want the system to allocate for EMM page frames.
REM The value must be given in Hexdecimal.
REM 0x1000 <= BaseSegment <= 0x4000. The value is rounded down to
REM 16KB boundary. The default value is 0x4000
REM RAM
REM specifies that the system should only allocate 64Kb address
REM space from the Upper Memory Block(UMB) area for EMM page frames
REM and leave the rests(if available) to be used by DOS to support
REM loadhigh and devicehigh commands. The system, by default, would
REM allocate all possible and available UMB for page frames.
REM
REM The EMM size is determined by pif file(either the one associated
REM with your application or _default.pif). If the size from PIF file
REM is zero, EMM will be disabled and the EMM line will be ignored.
REM
REM Add in EMM=RAM 7/6/02 for Mom and changed file=40 to 20
EMM=RAM
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=20
|
|
|  |
 |
|
wervdon
|
|
I've tried and tried to get it to work on my win2k machine (toshiba laptop). It just won't go no matter what I do to the pif and/or the config.nt file.
What I'm seeing is that there is no space available to actually load emm in the 1000 to 4000 block the comment states it requires:
C:\DOCUME~1\500755~1>mem /d
Address Name Size Type
------- -------- ------ ------
000000 000400 Interrupt Vector
000400 000100 ROM Communication Area
000500 000200 DOS Communication Area
000700 IO 000370 System Data
CON System Device Driver
AUX System Device Driver
PRN System Device Driver
CLOCK$ System Device Driver
COM1 System Device Driver
LPT1 System Device Driver
LPT2 System Device Driver
LPT3 System Device Driver
COM2 System Device Driver
COM3 System Device Driver
COM4 System Device Driver
000A70 MSDOS 001630 System Data
CLOCK$ System Device Driver
COM1 System Device Driver
LPT1 System Device Driver
LPT2 System Device Driver
LPT3 System Device Driver
COM2 System Device Driver
COM3 System Device Driver
COM4 System Device Driver
000A70 MSDOS 001630 System Data
0020A0 IO 001450 System Data
KBD 000CD0 System Program
HIMEM 0004E0 DEVICE=
XMSXXXX0 Installed Device Driver
0000B0 FILES=
000030 FCBS=
000170 LASTDRIVE=
003500 COMMAND 000A20 Program
003F30 MSDOS 000070 -- Free --
003FB0 COMMAND 000680 Environment
004640 DOSX 0087A0 Program
I've tried alot of changes to the config.nt and by lowering files to 10 and stack to the min, etc. I finally managed to get that block from 3F30 to 3FB0 to go free, but its just not enough free space for the ems driver to load.
Not sure what else can be done really, for now I've just given up.
|
|
|  |
 |
|
boolybooly
|
|
This thread discusses a bunch of tweaks for XP that may be worth checking out wervdon and others if you have not done so already.
|
|
|  |
All times are GMT. The time now is 05:33. Apolyton Time is 00:33. |
top of page
|
|
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is ON
vB code is ON
Smilies are ON
[IMG] code is ON
|
|
|
|
|
|