Shoutbox

it is though because in the past i have loaded the same programs i am trying now successfully on this computer.  As well, some of my up to  date software's installers are having the same popup when i try to open it.   

An up-to-date-installer wouldn't be 16-bit, so that error couldn't pop up for it. If all this is exactly as you've said, then you have some major problems with your XP installation...

Also, when you say "in the past", do you mean on a XP/NT machine?

Also, running a 16-bit game in an NT environment isn't strait-forward at all, and almost each individual program does need individual tweaking to be able to run decently in NT/XP (and this tweaking can involve many many things, from editing autoexec.nt/bat/dos files or config.sys files, to altering settings in the program itself, to editing the registry). And because there are millions of "old" 16-bit applications it isn't that easy to help you (unfortunatly), if you don't know much about computers....

XP solved it partly with the compatibily wizard, but that will not solve every possible problem (for the above reasons)...

But after reading this thread, my first suggestion would be, make sure your XP installation is in top condition and is installed absolutly properly without any twirks and hitches....

yes when i say in the past i mean on this exact Windows Xp Pro

quote:

---

Originally posted by LoochTheMan
it is though because in the past i have loaded the same programs i am trying now successfully on this computer.  As well, some of my up to  date software's installers are having the same popup when i try to open it.

---

Newer Installers can have the problem but it should have been resolved but putting a new Autoexec.nt in the systemroot.

quote:

---

Originally posted by Matty.

quote:

---

Originally posted by LoochTheMan
it is though because in the past i have loaded the same programs i am trying now successfully on this computer.  As well, some of my up to  date software's installers are having the same popup when i try to open it.

---

Newer Installers can have the problem but it should have been resolved but putting a new Autoexec.nt in the systemroot.

---

i never put a new Autoexec.nt in system root.  explain to me how so i can try that method