DOS-based update reports "autoexec.nt not suitable for running msdos 1

[MALFIE]

Actually it goes on to say " MS Dos & Windows applications".

Its an update file of the kind that has a "vanilla flavoured" icon,that when ran usually shows a dos-type window screen while it extracts a lot of files.. then it goes on with a typical windows installation process..
It's not just this file, it seems.. others that I have, that have worked fine previously, all do the same..
I've restored back to much earlier date/s but it isnt successful.
I dont know if I've run any of these since going to SP2 but I certainly would hacve with SP2 Beta.
Anyone have a suggestion??


"We do not stop playing because we are old, more likely we grow old because we stop playing...

 

[NickFerrar]

After applying the recent October security patches from MS we're getting this error on a lot of workstations with DOS apps. Haven't fixed it yet, info on the web to fix it hasn't worked for us.

 

[gpalmer711]

The following has help me on several occasions

http://support.microsoft.com/?kbid=324767

Greg Palmer
Free Software for Adminstrators

http://www.palmersoft.co.uk

 

[MALFIE]

Thanks for that... I have done exactly as the site suggested but now I've only achieved in removing the message.. the dos windows takes a few seconds to appear then about 2 secs to close..
Its a 360Meg file so it should take a while, and besides I usually see rapidly scrolling extractions taking place...

Oh why do they do this..??





"We do not stop playing because we are old, more likely we grow old because we stop playing...

 

[MALFIE]

Is it possible to extract the files on another XP machine (without recent updates.. I'd even do a new install on a spare pc) and somehow copy the installation files over..

I'm not hoping..


"We do not stop playing because we are old, more likely we grow old because we stop playing...

 

[gpalmer711]

Try starting the application for a dos box, this should allow you to see the error message that it is generating.

Start > Run > CMD > OK

type start /b <path & file name of your file>

Once you have the error that it is generating let us know what it is.

Greg Palmer
Free Software for Adminstrators

http://www.palmersoft.co.uk

 

[MALFIE]

Ok...

It just says

program too big to fit in memory

I tried another.. smaller ( 8.732,292 bytes) and it said the same thing..

Strange?




"We do not stop playing because we are old, more likely we grow old because we stop playing...

 

[MALFIE]

Just a thought..

some time ago I was seeking help here on a dos based program not being able to print under XP..

I thought I read that there was a different "command" for Nt other than CMD or command and that it was better suited to running dos apps under nt..

Am I dreaming? Does it matter ??


"We do not stop playing because we are old, more likely we grow old because we stop playing...

 

[gpalmer711]

See if any of the following help

http://forums.thatcomputerguy.us/index.php?showtopic=6620

http://forums.techguy.org/archive/index.php/t-125679.html

http://www.cybertechhelp.com/forums/archive/index.php/t-20914.html

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q315589

Greg Palmer
Free Software for Adminstrators

http://www.palmersoft.co.uk

 

[Mike2287]

I think I just ran into the same problem. the DOS App we use was running fine yesterday. The system is at a remote site so i couldn't get to deep into it but what I did was copy my autoexec.nt config.nt and command.com and put it in the system32 directory and that fixed it. There was also a lot of Ad crap on the system that I had to clean off remotely.

Mike