deleted hdd and cdrom drivers by mistake 1

[monkeywrench2]

I have Thinkpad 770x, win98, 128mb ram, 8gb hdd, cd/dvd, no floppy, no network.

I had driver conflicts and while trying to figure out which drivers went to which device, I stupidly deleted the ones that were controlling the cdrom and hdd. Now, of course, it has nothing to work with.

Can someone advise how to revive it?

Thanks, Ken

 

[soaplover]

does your windows start at all ?

 

[monkeywrench2]

No, Windows will not start. Graphic of inserting media in drive and f1 key blinking, cd door will not respond, hit f1, Black screen, 19990305 appears

Starting and holding down f2 gets into setup, but enabling cd and hd at startup no longer work.

 

[soaplover]

Have you tried holding down the "Ctrl" key or "F8"
during boot to force system into "safe mode"

//soaplover

 

[monkeywrench2]

OK, the HDD and Windows are going, but cdrom is not. I still have a conflict with two IDE controllers on the HDD, but seems to work ok.

I've enabled the cdrom at startup, but no luck. Device manager is not showing the cdrom as such. Is it called by some other name? I suppose the driver resides on hdd, but add new hardware fails to find the drive.

 

[soaplover]

That's because i asume it's already there but without your
drivers.
If you see the cdrom under device manager delete/uninstall it and reboot .

 

[monkeywrench2]

CDrom is NOT there. Here's what is there:
Disk drives
generic ide disk type<7
generic nec floppy disk (I don't have one)
Floppy disk controllers
Standard Floppy Disk Controller
Hard disk controllers
Intel xxxPCI Bus Master IDE Controller (this one has conflict)
Standard Bus Master IDE hard Disk Controller

nothing else in the way of disk drives

 

[soaplover]

delete both ide controllers and reboot..

 

[monkeywrench2]

OK, it found the Intel PCI ... controller and the Standard IDE controller and installed them both; the prior still has a conflict. Still no CD/DVD!

 

[soaplover]

If the conflict is no IRQ assigned .
Try disabling som other devices like LPT port Com port sound etc. Or try to set configuration manually on the failing ide device (not automatic) study the i/o and memory adresses that they dont conflict with used ones.

...

 

[soaplover]

I think the cdrom is connected to the ide controller you have problems with. Solving that one is the way to go.

...

 

[monkeywrench2]

I can't figure it out. Starting in SAFE mode, the cd/dvd is there: Matshita dvd rom... , but not in regular mode. The conflict persists around the HD and deleting a driver just makes the thinkpad reinstall it next time.

Question: why does it think I have a floppy drive when I don't? I delete the FDD and it finds the hardware and reinstalls the driver for it, too.

I doubt if it's a clue, but modem doesn't work either.

thanks soaplover for your help to now.

 

[soaplover]

can you find a file on your system under c:named bootlog.txt.
If so open it i notepad and copy it into the forum.

 

[milomorai]

do you have or can you get the drivers for the mobo of the laptop? they need to be reinstalled and the best thing to do is to get to the mfgr's web site, download the latest version of the mobo's drivers and install them-should get all mobo functions back to normal.

gavi

 

[monkeywrench2]

From Soaplover: &quot;can you find a file on your system under c:\ named bootlog.txt. If so open it in notepad and copy it into the forum.&quot; -No, that file doesn't exist on my computer.

From gavi: do you have or can you get the drivers for the mobo of the laptop? -If I could find them, I have no floppy drive and neither the cd or modem work.

 

[soaplover]

Start holding down &quot;left ctrl key&quot; .
Using the Windows 98 Startup Menu, choose Option 2: Logged. This creates a file called BOOTLOG.TXT in the root of the startup drive. When the boot fails, you can restart in Command Prompt Mode of safe mode .

//soaplover

 

[monkeywrench2]

I proceeded as instructed, it looked llke it produced a log, but came back to the startup screen, then proceeded on it's own with a normal boot to win98. The bootlog file was NOT produced.

 

[soaplover]

You can try step by step loading/start
A diagnostic startup of Windows is used to selectively load or not load drivers and environmental variables. You generally use this type of startup to pinpoint the exact driver causing a problem.


Step-by-step
During a step-by-step startup Windows asks you whether it should load or not load specific drivers. The main advantage of this startup is that you eliminate all the DOS level drivers and environmental settings. You can selectively load or not load drivers and applets contained in the registry and the System.ini and Win.ini files.

The following table shows the prompts you will see and how you should respond to them. Please keep in mind that there will be some variations in file locations and what is listed. If you do not see a prompt or you get an unexpected prompt, do not worry. If you choose not to load a driver that Windows needs, you'll likely end up at a command prompt. Start over and answer &quot;Yes&quot; to that prompt the next time.

Driver to load Response Why that response?
Load DoubleSpace driver
NOTE: You may or may not be prompted for this. Yes Necessary if you use disk compression. Otherwise, it has no effect. Loading it is precautionary.
Process the system registry? Yes Otherwise, you might as well start in Safe Mode
Create startup log file? Optional Your choice
Process your startup device drivers (Config.sys)? No This will bypass any DOS-level device drivers.
DEVICE=C:\WINDOWS\HIMEM.SYS Yes Windows needs this to work.
DEVICE=C:\WINDOWS\DBLBUFF.SYS
NOTE: You may or may not be prompted for this. Yes If you're prompted for this, Windows needs it
DEVICE=C:\WINDOWS\NLSFUNC.SYS Yes Loads country specific information
DEVICE=C:\WINDOWS\IFSHLP.SYS Yes Windows needs this to work.
Process your startup command file (Autoexec.bat)? No This will bypass any DOS level drivers and environmental settings.
Load the Windows graphical user interface? Yes Otherwise, you might as well start in Command Prompt.
Load Windows drivers? Yes This will assist you in determining what drivers Windows is loading and the order in which they are loading.

The Windows drivers you need to load depend on what you are troubleshooting. For example, if you are trying to resolve a problem that you believe involves the Symantec event handler (Symevnt), then you would click &quot;No&quot; to the prompt for Symevnt.386.