can't boot after repair

[eric]

I think my problems began after installing a new HDD.
I've since found out that my mother board is only
designed to take a max of 120G, I bought 160G. I was able
to install it and the driver that came with it and all
160 G were recognized and it seemed to be working but XP
would freeze in the middle of laoding large avi files
onto the new HDD. (I hadn't yet realized the HDD might be
the problem, duh). For a long time I hadn't been able to
use msconfig and ignorantly thinking this might help me
figure out the problem I came to this forum to ask advise
in getting it to run again. I ended up attempting a
system repair and this is where the current problem
begins.

During the system repair the process stalled out at 34
minutes but i let it run overnight and finally a window
came up alerting me that it couldn't load the installer
for TapeController. It then sluggishly continued the
repair after restarting itself several times and I was
able to boot up. after a few minutes, during an attempt
to re-install the updates, it crashed and i haven't been
able to boot it up again. I've tried repairing it
several times, the same error message is given, but it
won't complete the process to boot. I'm just left with a
black screen and moveable cursor. I have re-installed
(hopefully temporarily) XP onto a new partition and I can
access the other partition and even run programs off of
it, I just can't boot to it.

I think i need to uninstall the 160G HDD driver and
whatever TapeController is. Is it possible to uninstall
drivers from an OS which doesn't boot? Any other
suggestions? Here are the error messages in pnpwfdc and
setupapi where I found references to tapecontroller if
this helps: Thanks Eric


(pnpwfdc)

[Unknown]
%Unknown.DeviceDesc% = Unknown_TDC_Inst,
TapeController\Unknown
%Clone.DeviceDesc% = Clone_FDC_Inst, CLONEFDC

[Aiwa]
%Aiwa.DeviceDesc% = Aiwa_TDC_Inst, TapeController\Aiwa

[Alloy]
%Alloy.DeviceDesc% = Alloy_TDC_Inst, TapeController\Alloy

[Archive]
%Arc20001.DeviceDesc% = Arc20001_TDC_Inst,
TapeController\Arc20001
%Arc4100.DeviceDesc% = Arc4100_TDC_Inst,
TapeController\Arc4100

[Conner]
%Conner.DeviceDesc% = Conner_TDC_Inst,
TapeController\Conner

[CMS]
%FC10.DeviceDesc% = FC10_TDC_Inst, TapeController\FC10
%FC20.DeviceDesc% = FC20_TDC_Inst, TapeController\FC20
%TC15.DeviceDesc% = TC15_TDC_Inst, TapeController\TC15
%AB10.DeviceDesc% = AB10_TDC_Inst, TapeController\AB10
%FC10.DeviceDesc% = FC10_TDC_Auto, FC10
%FC20.DeviceDesc% = FC20_TDC_Auto, FC20
%TC15.DeviceDesc% = TC15_TDC_Auto, TC15

[Exabyte]
%Exabyte.DeviceDesc% = Exabyte_TDC_Inst,
TapeController\Exabyte
%ExabytePnP.DeviceDesc% = ExabytePnP_TDC_Inst, *EXA4242

[Iomega]
%IHA10p.DeviceDesc% = IHA10p_TDC_Inst,
TapeController\IHA10p
%IoAccel.DeviceDesc% = IoAccel_TDC_Inst,
TapeController\IoAccel
%IoDitto.DeviceDesc% = IoDitto_TDC_Inst,
TapeController\IoDitto
%IoPnP.DeviceDesc% = IoPnP_TDC_Inst, *IOM1230
%IoPnP4mb.DeviceDesc% = IoPnP4mb_TDC_Inst, *IOM0040

[Maynard]
%Maynard.DeviceDesc% = Maynard_TDC_Inst,
TapeController\Maynard

[Mountain]
%Mach2.DeviceDesc% = Mach2_TDC_Inst, TapeController\Mach2

[National]
%National.DeviceDesc% = National_TDC_Inst,
TapeController\National

[Summit]
%Accel.DeviceDesc% = Accel_TDC_Inst, TapeController\Accel
%Avalanche.DeviceDesc% = Avalanche_TDC_Inst,
TapeController\Avalanche

[Tallgrass]
%Tallgrass.DeviceDesc% = Tallgrass_TDC_Inst,
TapeController\Tallgrass

[Teac]
%Teac30x.DeviceDesc% = Teac30x_TDC_Inst,
TapeController\Teac30x

[Tecmar]
%Tecmar.DeviceDesc% = Tecmar_TDC_Inst,
TapeController\Tecmar
%TecPnP4mb.DeviceDesc% = TecPnP4mb_TDC_Inst, *TEC0040

[Wangtek]
%Wangtek.DeviceDesc% = Wangtek_TDC_Inst,
TapeController\Wangtek

[Unknown_TDC_Inst]
AddReg = Unknown_AddReg
LogConfig=unknownlc1,unknownlc2






(setupapi)

#-199 Executing "C:\WINDOWS\system32\setup.exe" with
command line: setup -newsetup
#-147 Loading class installer module for "Tape drive
controllers".
#E360 An unsigned or incorrectly signed
file "C:\WINDOWS\System32\pnpwhsc.dll" for driver "Tape
drive controllers" will be installed (Policy=Ignore).
Error 2: The system cannot find the file specified.
#E144 Loading module "C:\WINDOWS\System32\pnpwhsc.dll"
failed. Error 126: The specified module could not be
found.
Windows could not load the installer for TapeController.
Contact your hardware vendor for assistance. Error 126:
The specified module could not be found.
[2003/07/14 04:44:54 556.1771 Driver Install]
#

 

[AWM]

I think my problems began after installing a new HDD.
I've since found out that my mother board is only
designed to take a max of 120G, I bought 160G. I was able
to install it and the driver that came with it and all
160 G were recognized and it seemed to be working but XP
would freeze in the middle of laoding large avi files
onto the new HDD. (I hadn't yet realized the HDD might be
the problem, duh). For a long time I hadn't been able to
use msconfig and ignorantly thinking this might help me
figure out the problem I came to this forum to ask advise
in getting it to run again. I ended up attempting a
system repair and this is where the current problem
begins.

One way round might be to use a cheap IDE ATA RAID controller card and plug
your single HD into this (the raid card will be quite happy to boot from
with just a single HD but obviously won't offer RAID until you fit another
drive or drives), the RAID card has its own BIOS so the max avaialable hard
disk size in the PC's own bios won't matter. To the PC and the operating
system the RAID card looks v ery much like a SCSI interface device.

 

[eric]

Thanks for helping R.C.,

I hope I haven't confused things by assuming my inability
to boot to my repaired old XP installation (which BTW is
on a patition on 80 G HD)stems from my attempt to install
the larger HD. I'm not positive that is the problem. I
have removed the new HD but the driver still remains on
the OS and since I can't boot to that OS I don't know how
to uninstall it. (I think this is the main question, how
can i uninstall this?) Eventually using the large HD may
be a different issue (I'm not sure). I hope I am not
being redundant. (not being ignorant is out of the
question)

So, I did copy the string you said to copy. it is
08/09/2001-VT8366-8233-6A6LVS29C-00. I haven't yet
figured out where at wimsbios I am supposed to use that
info, I'll keep looking.

My mobo is Soyo SY-K7V VIA KT 266 (AMD Socket-A). There
hasn't been a new BIOS upgrade posted there since I
installed it. Iwrote to SOYO to ask for info about
installing larger HDD's. I'll keep looking at the other
websites you listed.
Thanks again, Eric