If it were my PC, I'd edit the autoexec and kill that line about the readme on Q.
Can't do any harm in whipping it out and trying again.... you can always go back and re-edit autoexec to put it back...
You have the option to make a bootdisk somewhere within Windows - perhaps you can access it in Safe Mode.Originally Posted by ajbrun
I have a Windows ME bootdisk, but I overwrote my last 98 one only a few weeks ago.
I have been able to create a boot disk within safe mode. But that doesn't seem to give me any CD drives in safe mode. I'm just about to do a search for one with ATAPI drivers on....
I would do that now, but my mum has just started a virus scan for some reason, and even though I tell her I just did one yesterday, seh won't let me cancel .Originally Posted by Deckard
EDIT: For the ATAPI startup disk thing, I think windows creates that when you click create startup disk. Using that I'm able to access a CD ROM in DOS. But when I try to open what I think it the correct file, it says "this must be run using win32". AFAIK, this means using windows 95, 98 XP etc. Therefore, I need to access the disk drives whilst in safe mode.
I have another idea. I have a linux CD that is able to boot from the CD, and give a sort of limited example knoppix linux distro. Is there anything similar for windows? I'm thinking of booting from that. Starting windows from the CD, and accessing my other CD drive which has the 98 disk in, and do a system restore. The reason I can't do it in knoppix (or DOS) is that it has to be a win32 appliacation (see above).
**************************************
Like I said earlier, I don't like to dominate a thread with loads of my own posts, so I'll just edit this one .
I got it working!!!!!!!
I followed a guide that suggested renaming autoexec.bat and config.sys to .tmp files. It seems to work like this, but that suggests that there was something within those files that was acusing the problem. Is it a good idea to just leave it like it is not (autoexec.tmp), or should I rename them to how they were and try to figure out which part of the file was wrong?
The thing I followed is the "fith step" on this page.
It does say to try and find the line that's incorrect, but there really are quite a lot of options in step by step confirmation, so if it's safe to run it as it is, I'd rather leave it.
Also, Deckard - I tried removing the Q\readme line, but that didn't work.
I don't think there's anything in autoexec or config that's absolutely needed by Windows, but what tou could do is some easy troubleshooting:
1. Put config.sys back - if there's a problem you know that's what the issue is, if not leave it there.
2. Whichever file is causing the problem (let's assume it's only one for now) just remark out every line - add rem plus a space to the start of any line that doesn't have it already. Then remove the rems one at a time (having made a note of which lines are new).
There are currently 1 users browsing this thread. (0 members and 1 guests)