+  RHDN Forum Archive
|-+  Romhacking
| |-+  ROM Hacking Discussion
| | |-+  HUGE problem with spasm
Pages: [1]
Author Topic: HUGE problem with spasm  (Read 585 times)
Gemini
Guest
« on: July 13, 2007, 03:11:44 am »

This is a pure DOS program (compiled with DJGPP I guess), but it's supposed to work on Windows XP, and it was, until now. The other day I noticed a strange error while trying to open the program twice on the same prompt window. It was saying "Load error: no DOS memory", then killed the process. Now, how could it have no memory for DOS when I have 1 GB of ram!? Even trying expanding DOS memory or setting various modes didn't change a thing. Then I thought it could be SP2's fault, so I removed it and switched to SP1a. Nothing changed, I got again the same error. So, this time I tried reinstalling the basic XP with no SP at all, but I got again the same error message. >_>
The funniest thing about this is that my old computer was working fine with spasm, even though it had only 256 MB of ram, same for my mother's laptop.

Anybody knows a solution for this problem? And please, no DosBox. I can't really stand that crap. :/
creaothceann
Guest
« Reply #1 on: July 13, 2007, 05:44:24 am »

Virtual PC Smiley
Gemini
Guest
« Reply #2 on: July 13, 2007, 06:33:28 am »

I was asking for an actual solution. Virtual PC and DOS box are just a cheap way around.

Anyway, looks like spasm works for other people with more ram than me. >_<

[edit]Problem solved! I just replaced the original stub with cwdstub.exe and recreated the spam.exe. Here it is, for anybody with the same problem I had.

I'll add it later to the database, too.[/edit]
« Last Edit: July 13, 2007, 07:05:17 am by Gemini »
creaothceann
Guest
« Reply #3 on: July 13, 2007, 12:43:51 pm »

Just for the record, it seems unlikely that the amount of actual RAM matters much.

DOS programs always had to find their own ways to access memory > 16 MB, which is the maximum for EMS/XMS iirc. Protected Mode programs probably have better access, but a bug in the DOS extender could interfere with the OS.
Gemini
Guest
« Reply #4 on: July 13, 2007, 02:16:16 pm »

The problem is I don't have a clue what caused that bug. My software configuration is just the same I had on my old computer, but somehow it's not working with the original stub. I thought it was the RAM amount because DOS is unable to manage more than 16 MB, but several tests on different machines made me change my opinion.

Available on rh.net, too.
« Last Edit: July 14, 2007, 07:12:31 am by Gemini »
Skeud
Guest
« Reply #5 on: July 14, 2007, 03:30:14 pm »

I have "Exiting due to signal SIGSEGV" error with your new version, without even loading a file...  Cry
Gemini
Guest
« Reply #6 on: July 14, 2007, 05:04:05 pm »

Heh, go figure why. >_> Take a look at this, maybe it can help. It's the package I used for making that exe with the new stub.
Pages: [1]  


Powered by SMF 1.1.4 | SMF © 2006-2007, Simple Machines LLC