Post by Keith Heitmann on Mar 17, 2005 9:57:44 GMT -5
Well, I had one of those gotcha computer moments this morning.
I went to edit my webpages and opened a MSDOS window and typed my batch file name to launch EDIT.COM and my files and got a message that my autoexc.nt wasn't "suitable" to run the application.
Bummer. Luckily I had seen this posted on the boards I moderate before and new where to get the help file I needed.
So I open the Windows support data base on the problem and followed the first steps to expand the files off the Windows CD to the system32 folder of Windows on my hard drive. No luck.
I was prepared to carry out the second step by copying and pasting some lines to notepad and saving them as the new Config.nt, Autoexec.nt files but then I thought they didn't seem to be as complete as my previous ones proably were.
So I looked down the page a little and found the final step, which was to copy the two .nt files from the C:\Windows\Repair folder and then set each new copy in my system32 folder to Read-Only. Success. Whew.
I hate it when stuff like that happens, but luckily it took about 20 minutes fix.
I think the files got corrupted last night while I was downloading a PDF file. It seemed to hang and I called up the Taskmanager to close the download, but for some reason when it opened on the processes window instead of the applications window I ended the acrobat process I saw on the list.
Bad idea. I should have used the end task option to close acrobat reader from the applications list instead I guess.
I went to edit my webpages and opened a MSDOS window and typed my batch file name to launch EDIT.COM and my files and got a message that my autoexc.nt wasn't "suitable" to run the application.
Bummer. Luckily I had seen this posted on the boards I moderate before and new where to get the help file I needed.
So I open the Windows support data base on the problem and followed the first steps to expand the files off the Windows CD to the system32 folder of Windows on my hard drive. No luck.
I was prepared to carry out the second step by copying and pasting some lines to notepad and saving them as the new Config.nt, Autoexec.nt files but then I thought they didn't seem to be as complete as my previous ones proably were.
So I looked down the page a little and found the final step, which was to copy the two .nt files from the C:\Windows\Repair folder and then set each new copy in my system32 folder to Read-Only. Success. Whew.
I hate it when stuff like that happens, but luckily it took about 20 minutes fix.
I think the files got corrupted last night while I was downloading a PDF file. It seemed to hang and I called up the Taskmanager to close the download, but for some reason when it opened on the processes window instead of the applications window I ended the acrobat process I saw on the list.
Bad idea. I should have used the end task option to close acrobat reader from the applications list instead I guess.
!!! Sounds all but TOO familiar. I had a similar occurance awhile back and my file did get corrupted. Of course I was downloading something at the time too. So, do we see a pattern here 
?! What I'm saying is be careful during ANY download, and if you have a problem, you can bet that's what it is.