Stop SNASM from crashing!

Talk about development tools here

Moderator: BigEvilCorporation

Post Reply
Charles MacDonald
Very interested
Posts: 292
Joined: Sat Apr 21, 2007 1:14 am

Stop SNASM from crashing!

Post by Charles MacDonald » Wed Jan 12, 2011 2:23 am

Sometimes SNASM68K crashes as soon as you invoke it under Windows XP. This problem has been driving me nuts, but here is the solution:

Make sure your PATH environment variable is 250 characters or less.

That's it! You can type "path" in the command prompt to see how big it currently is, and set up a batch file invoke a prompt with a more limited path to work around this problem.

In general, restricting the PATH size will prevent any program that uses DOS4GW from crashing immediately. :D

TmEE co.(TM)
Very interested
Posts: 2440
Joined: Tue Dec 05, 2006 1:37 pm
Location: Estonia, Rapla City
Contact:

Post by TmEE co.(TM) » Wed Jan 12, 2011 8:48 am

Use the 98/NT/2K/XP version instead ?
Mida sa loed ? Nagunii aru ei saa ;)
http://www.tmeeco.eu
Files of all broken links and images of mine are found here : http://www.tmeeco.eu/FileDen

Pascal
Very interested
Posts: 200
Joined: Wed Nov 29, 2006 11:29 am
Location: Belgium
Contact:

Post by Pascal » Wed Jan 12, 2011 2:32 pm

good to know, thanks charles !

Charles MacDonald
Very interested
Posts: 292
Joined: Sat Apr 21, 2007 1:14 am

Post by Charles MacDonald » Wed Jan 12, 2011 7:14 pm

TmEE co.(TM) wrote:Use the 98/NT/2K/XP version instead ?
Ah, I should have clarified: this is a fix _for_ the 98/NT/2K/XP version. :D

My problem is that it would work for a while and then stop working, and now I realized it's because I installed and removed software which adjusted the PATH length.

On another forum somebody was debugging some productivity software that used DOS4GW and mentioned the hard-coded PATH limit, and that's what fixed it.

cdoty
Very interested
Posts: 117
Joined: Wed Nov 29, 2006 2:54 pm
Location: Houston, TX
Contact:

Post by cdoty » Fri Jan 21, 2011 3:09 pm

Charles MacDonald wrote: On another forum somebody was debugging some productivity software that used DOS4GW and mentioned the hard-coded PATH limit, and that's what fixed it.
Ahh, that explains some other software that seemed to work for random reasons.

Post Reply