Problem with autoexec.nt

Hi all - hope you can help. I have been getting the message upon booting up and when loading some programs:

c:\windows\UI\BIOSCTL.EXE
c:\windows\system32\autoexec.nt. The system file is not suitable for running MS DOS and Microsoft Windows applications. Choose close to terminate the application.

Well... I've searched this BBS and haven't found anything specific that has helped me fix this. I have checked the file via the command prompt.

When I searched for the file initially in the system32 directory, it wasn't found. I did find a autoexec.nt in the windows\repair directory so I copied it to the windows\system32 directory.

I reviewed the autoexec.nt and the config.nt - now both in the system32 directory, both are correct.

Still, I get the error message.

I have only a windows recovery disk from the company I purchased the computer from - I'm afraid to put this in the cd drive! I don't want to end up back at square one like the day I bought the computer ... I hate the thought of starting over!

I'm not sure what to do - do I need to go buy Windows and do some sort of repair/reinstall?

Any help will be appreciated.

Thanks,
krec

 

Autoexec.nt and config.nt are only needed when you try to install or run 16 bit (older DOS) applications that need them. They have nothing at all to do with XP startup.

This article will walk you through making sure all is well for that instance.

If this particular error is happening when you boot up, something is wrong. Also, the only mention of c:\windows\UI\BIOSCTL.EXE I can find with some searching is from another post on another forum where the poster had the same symptoms as you. No responses to him.

Based on the fact that no internet site seems to mention that folder or that file, I have to think 'virus' until proven otherwise. Do a full scan /w the option to fix any problems from the RAV site (see quicklinks in my signature).

 

Thanks for your quick response to my question...

I have acually already found that site with the fix .. .my question is - it looks like it wants to expand files on a windows cd - I don't think this means my windows recovery cd that came with my computer - does it?

Do I need to go buy windows xp to do this?

I have also scanned for virus and trojans using many different softwares - I will go try the RAV as you recommend.

The error may be showing up as I boot because it is loading a 16 bit program as windows loads...

If you think of any other suggestions, please let me know. As I mentioned, I really don't want to do a reinstall from a recovery disk and start from scratch to fix this - I'll buy Windows before I do that!

Thanks again,
krec

 

The error may be showing up as I boot because it is loading a 16 bit program as windows loads

That would certainly account for your seeing the error.

I imagine you can find copies of the files on your recovery CD and if you restore just those, it shouldn't cause a problem. Look for an I386 folder on the CD and also on your hard drive. Some PC makers who only provide a recovery CD will be nice enough to put the folder on the hard drive.

I'd also usually recommend against loading a 16bit app at startup unless there was some compelling reason for it.

Re: the possible virus - I recommended an online scan since quite a few of the viri out there these days can disable your onboard AV but have it still appear to be working. Sneaky buzzards!!!

But it may not be needed. Your old app could be trying to run from c:\windows\ui and the autoexec.nt and config.nt problems could be causing that .exe I couldn't identify to give an error.

 

Hi Newt...

I think I found the problem...

First I followed the second half of the directions at the site you pointed me to - created a new autoexec.nt in word pad and copied it to the system32 folder.

That did not do the trick... so I started focusing on the windows\UI folder and what is in that - that led me to a program called GAINWARD Expertools that loads a file called TBPanel at startup.

I stopped it from loading and no more error message.

It was really just a "find a needle in a hay stack" locating the origin of the error message. But I think I'll be able to sleep tonight now!

Thanks for all of your suggestions.

krec

 

Glad you found it.

I'd be real wary about using anything having 'tools' in the name and old enough to be 16 bit on an XP machine.

If there are things you use that app to do, say what and we can probably dig up some 32bit ones that will work for you and more safely.

 

Still having a problem with Autoexec.nt

Hi... I have tried several methods of replacing the autoexec.nt file including replacing it with the one in the i386 folder on my windows operating cd - no luck. Can't even get a dos window to open up by using command.com via the start...run...open. Checked the config.nt and the autoexec.nt in wordpad and they look ok to me. I have read athe windows support document 314106 and am not sure I understand what the method of testing and fixing a problem with NTVDM is - can anyone shed some light on that - it looks pretty complicated to me.

I do have an old program that I love to use - Corel Ventura Publishing and Corel Draw version 5. I purchased these years ago and they do what I need and I haven't bothered to upgrade them. However, since the glitch with the autoexec.nt file and error, I can't get them to even load.

I hate to go out and pay for upgrades on this bundle of programs that I use from time to time - they are not inexpensive! Anyone know of anything else I can try to get my 16 bit programs to work?

Thanks for any suggestions.

krec

 

krec - this sort of thing is nearly impossible to troubleshoot via the forum. Too many possibilities.

I have had some luck in the past getting 16bit stuff to run and then sending the specifics to the user having the issue.

If you have apps that are small enough to zip and send via email or if you have a web site to store them where the can be downloaded, I'll be happy to play around with your 2 or 3 most critical ones and see if I can get them running.

The Corel ones are too big for this to be reasonable. Your best bet there is to dig through the documentation (manuals or whatever you can find on the internet) about specific values they put in autoexec.bat, config.sys, or any windows .ini files and try to create an environment they like. Also and if you haven't already tried, if you can create a shortcut and set it for the oldest compatibility mode possible, they may behave better.

At some point, OS development will go beyond anything that will allow these older apps to run though. Maybe it has already happened but maybe not and it will be Longhorn that finally breaks them.

 

Thanks,

I know you are right about eventually losing all ability to use these in the windows environment. I did some checking and found that I will have to buy the entire new release of these as they upgrade from version 7 up - I have 5! Seems like I should get some sort of discount for that, though!

I did try to run them in a different compatibility mode - no luck. And I would be happy to have you try to tweak the software if you can figure out a way to do that. If you want to brainstorm, I'll be happy to send you my email address - let me know.

If I were to try to edit the autoexec to run the Corel programs, do I edit the autoexec.nt and config.nt files? I remember doing that years ago - I loved dos and tweaked the autoexec.bat and config.sys files lots of times with great results - is this the same sort of thing? Dos always made so much sense to me - I went into the windows environment kicking and screaming!!

Would it be possible to purchase a second hard drive (maybe an external one) and run windows 98 on it - I had no problem running these programs on windows 98. Or do you think that would be too much trouble than it is worth. Or... maybe I could network an older computer using windows 98 to my current computer using windows xp - and access that program from that older computer - can I mix the operating systems like that? Would either of these ideas work? Just thinking outloud!

Thanks for your help,
krec

 

You can certainly add a drive and run 98 on it. Easier to do if you start with 98 and add XP but you can still tweak things around so you have a choice at boot time of which OS you want to load.

With the older apps installed to the 98 drive/partition, they will run fine and not butt heads with XP at all.

 

Thanks, that just might be the way to go... do you know where I can get information to step me through that process? I have never run two operating systems before! And I'm not sure how to set it up so I get a choice which drive/operating system to boot.

Thanks for your help.

krec

 

If you have 98 installed first it will be automatic. You will do better with the operating systems on different drives or partitions so if you only have one now (C:\ maybe) you will need to do some work

Say how you are set up now and how you want to do the deed and we'll give specifics on getting you a dual boot system.

 

Thanks for offering to step me through this. I'm getting pretty frustrated with this stupid autoexec.nt error and not being able to do what I need to do!

One question though.... I've had this computer since last November - why is this acting up now? Any ideas?

Let me know if you need something that isn't listed here!

Pentium 4 3.0 ghz
512 mb ram
120 gig hard drive (c: drive)
dvd combo
dvd rw
zip drive
floppy
card reader
Windows XP Home Edition SP-1

Got these specs after running Belarc Advisor...

Controllers:
Controllers Display
Standard floppy disk controller
Intel(R) 82801EB Ultra ATA Storage Controllers
Primary IDE Channel [Controller]
Secondary IDE Channel [Controller]

Bus Adapters:
Bus Adapters Multimedia
VOB InstantDrive Controller
Intel(R) 82801EB USB Universal Host Controller - 24D2
Intel(R) 82801EB USB Universal Host Controller - 24D4
Intel(R) 82801EB USB Universal Host Controller - 24D7
Intel(R) 82801EB USB Universal Host Controller - 24DE
Standard Enhanced PCI to USB Host Controller


Multimedia:
BtCap, WDM Audio Capture
BtCap, WDM Video Capture
BtTuner, Philips WDM TvTuner
BtXBar, WDM Crossbar
Creative Game Port
Creative SB Live! series

Other Devices:
VIA OHCI Compliant IEEE 1394 Host Controller
Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
PS/2 Compatible Mouse
USB Mass Storage Device
USB Root Hub
USB Root Hub
USB Root Hub
USB Root Hub
USB Root Hub


Display:
NVIDIA GeForce FX 5200 [Display adapter]
BenQ FP731 [Monitor]


Thanks again,
krec

 

krec - I have no idea why it suddenly started acting ugly. We could probably figure it out if given enough time but probably not worth the effort.

I guess the question now is do you:

- Want to get a clean start for your dual boot system - scrub everything and start with installing 98 then install XP so you will have the option when you start up of which one you want and also be rid of any XP issues that have crept in or

- keep XP and add 98 then fiddle around to get the system to dual boot?

If you go with a clean start you will lose any XP settings and personal files you have now (so back them up to CD or something) and will have to reinstall all software but it is pretty much an easy install that almost never gives any problems.

If you want to keep XP and add on 98, you will at least have to buy a partition manipulating program (partition magic is a good one) to shrink the space that XP and C:\ take so you have some available drive space. Usually works well but tweaking partitions can mess up a system. OTOH, if something messed up all you would need to do is the same as you would do for a clean start.

Your choice and either option should work but the approach is completely different so we gotta know how you want to do the deed.

 

Hi Newt...

I really hate the idea of wiping everything off my existing hard drive - and I do understand that may just be what I have to do if partitioning goes wrong. Would it just be easier if I purchased a second hard drive? I'm not sure if I have room for another internal hard drive - would an external drive do the trick?

I do have a copy of Partition Magic 6.0 - for windows 95/98, windows me, windows nt 4.0 with sp4 applied or windows 2000 professional. Could I use this on the new drive and partition it with 98 ... maybe both 98 and xp?

What are your thoughts on that - and would I be able to do this and choose which drive to boot to? Would I be able to access both drives no matter which one I choose to boot with?

Thanks as always - I appreciate your help.

krec

 

I'll pass on the PM specifics. I have never used it and we have folks who use it regularly. Not even sure which version you need to mess around with XP.

A 2nd drive would certainly be a safer option. Lots cheaper and faster if you have room in the case for it though. Have you looked?

If you load 98 on a 2nd drive you can certainly get access to both operating systems. XP will be able to see and work with both. If your XP is set for NTFS, the 98 system won't be able to even see it but that would be true no matter how you set it up.

 

same error

I get the same error, C:WINDOWS\UI\BIOSCTL.EXE
C:\WINDOW\SYSTEM32\AUTOEXEC.NT. the file system not suitable for running ms-dos and ms windows apps. I also have TBPanel from Gainward, however disabling it, uninstalling it or reinstalling it doesn't solve the problem. Autoexec.nt doesn't seem corrupted, it's mostly comments. There must be something with tbpanel that persists after an uninstall.

 

Hi joe45 and welcome to the forum.

Is the app one you really need to continue using? It is possible, usually, to get these things working but it often takes lots of time and lots of messing around. If you still have an older system where it works and that uses autoexec.bat, posting the contents of that file along with config.sys would be a good place to start.

Better option is to use a newer piece of software if possible. What does the app do for you?

 

heres the fix

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

basically insert your win xp cd and in the command prompt type:
expand CD-ROM Drive Letter:\i386\autoexec.nt_ c:\windows\system32\autoexec.nt

windows loads autoexec.nt at startup by default and Im not sure how to prevent it, and don't really care that much but the error message at startup is rather anoying so there is the fix for it. Some web sites offer various programs to install to fix this problem but I hope you trust them.

 

I had the same same problem; I think I just fixed it.

First thing I did was to find the "BIOSCTL.exe" file in the specified folder, "C:\Windows\UI ". I ran the executable and was given the error message I have been recieving on boot up. Next, I went looking for "autoexec.nt ". I couldnt find the file in "C:\Windows\System32 ", where it was supposed to be. I did a search over my system for the file and it was found in "C:\Windows\Repair ". I took it from there and set it in the system32 file and reran "BIOSCTL.exe ". Now, I dont recieve an error anymore.
I don't know how the file got moved but, moving it back to the right folder seemed to fix the problem. I HOPE!
Good Luck Guys,
Turb