Discussion:
XP install says no file system on drive, but files are still visible
(too old to reply)
Lee@DVDDebate
2004-12-20 01:08:15 UTC
Permalink
I've just had a very strange problem after installing a webcam driver.
Upon completion the driver required a reboot, so off it all went. When
the machine came back up XP appeared to be booting OK, but then stopped
and went in to a boot loop. Upon closer inspection it seems there is a
blue screen with an error message appearing, but it flashes up way too
fast for me to read before it starts to reboot again and I'm not sure
how to turn the auto-reboot off in order to read it. BIOS somewhere, maybe?

Anyway, I tried booting to safe mode with no joy, then decided to
reinstall XP. XP install disc gets to the 'choose your drive to install
to' page and it lists my C drive but with no file system listed. Other
drives in the machine all show as NTFS. Odd, and not a little worrying.
Is the drive trashed, I wonder?

I spend a few minutes switching drives and jumpers around and eventually
get XP up and running on a whole new drive. My old drive is now slaved
as F: and, lo and behold, XP can see it fine and has identified it as
having an NTFS file system with all the files are still there and in
working order. A disc scan shows no errors on the disc.

Odd. So I switch everything back and try to boot from the old drive
again. No luck. Try XP install again and once more the install routine
says there is no file system on that drive.

I switch again, thinking I can just get the install app to re-install XP
on to the drive when it shows up as F:.

Still no good. Even when slaved, the XP install disc cannot find a file
system and insists that if I want XP on that drive it will need to be
completely reformatted. Which, considering it's a 100Gb drive with only
2% space left, I'm not really that keen to do.

I'm now completely stumped. Can anybody offer any suggestions as to what
to try next?

Thanks,

Lee.
Toolman Tim
2004-12-19 01:20:06 UTC
Permalink
"***@DVDDebate" <***@dvddebate.com> wrote in message news:mx4xd.42311$***@fe41.usenetserver.com...
| I've just had a very strange problem after installing a webcam driver.
| Upon completion the driver required a reboot, so off it all went. When
| the machine came back up XP appeared to be booting OK, but then stopped
| and went in to a boot loop. Upon closer inspection it seems there is a
| blue screen with an error message appearing, but it flashes up way too
| fast for me to read before it starts to reboot again and I'm not sure
| how to turn the auto-reboot off in order to read it. BIOS somewhere,
maybe?
|
| Anyway, I tried booting to safe mode with no joy, then decided to
| reinstall XP. XP install disc gets to the 'choose your drive to install
| to' page and it lists my C drive but with no file system listed. Other
| drives in the machine all show as NTFS. Odd, and not a little worrying.
| Is the drive trashed, I wonder?
|
| I spend a few minutes switching drives and jumpers around and eventually
| get XP up and running on a whole new drive. My old drive is now slaved
| as F: and, lo and behold, XP can see it fine and has identified it as
| having an NTFS file system with all the files are still there and in
| working order. A disc scan shows no errors on the disc.
|
| Odd. So I switch everything back and try to boot from the old drive
| again. No luck. Try XP install again and once more the install routine
| says there is no file system on that drive.
|
| I switch again, thinking I can just get the install app to re-install XP
| on to the drive when it shows up as F:.
|
| Still no good. Even when slaved, the XP install disc cannot find a file
| system and insists that if I want XP on that drive it will need to be
| completely reformatted. Which, considering it's a 100Gb drive with only
| 2% space left, I'm not really that keen to do.
|
| I'm now completely stumped. Can anybody offer any suggestions as to what
| to try next?
|
You say you were unable to get it to boot in safe mode - did you get the
boot menu? One of the options there is "Last known good configuration". You
might try that.

And when you try to run the XP install from the CD, you have other options -
a repair install and a recovery console. I don't remember if system file
scan runs in a recovery console...probably not, but in case I'm wrong, that
would be "SFC /SCANNOW". The repair install could possibly recognise your
existing OS install.

Oh - and if you have only 2% space left on your drive, you are asking for
problems (in my opinion). I never let mine get closer than 5% - and I prefer
10%. It gives your operating system room to move files around if needed.
Toolman Tim
2004-12-19 01:30:44 UTC
Permalink
"Toolman Tim" <***@my.email.is.invalid> wrote in message news:eP4xd.21055$***@fe05.lga...
|
| "***@DVDDebate" <***@dvddebate.com> wrote in message
| news:mx4xd.42311$***@fe41.usenetserver.com...
|| I've just had a very strange problem after installing a webcam driver.
|| Upon completion the driver required a reboot, so off it all went. When
|| the machine came back up XP appeared to be booting OK, but then stopped
|| and went in to a boot loop. Upon closer inspection it seems there is a
|| blue screen with an error message appearing, but it flashes up way too
|| fast for me to read before it starts to reboot again and I'm not sure
|| how to turn the auto-reboot off in order to read it. BIOS somewhere,
| maybe?
|<snipped>

I forgot to mention that the "restart after error" is part of XP and is one
of the first things to turn off when you get running again. Right-click "My
Computer" select "Properties", click on the "Advanced" tab and look for
"Startup and recovery" - click on settings there. Find "Automatically
restart" and turn that off.
Bruce Hagen
2004-12-19 01:38:25 UTC
Permalink
<snip>


And you also forgot to tell him not to cross-post unless
absolutely necessary, and to fix his clock so he isn't posting 24
hours in the future. <G>

B.
Kelly
2004-12-19 07:26:46 UTC
Permalink
But you just did so, all should be well?
--
Happy Holidays,
Kelly (MS-MVP)

Troubleshooting Windows XP
http://www.kellys-korner-xp.com
Post by Bruce Hagen
<snip>
And you also forgot to tell him not to cross-post unless absolutely
necessary, and to fix his clock so he isn't posting 24 hours in the
future. <G>
B.
Lee@DVDDebate
2004-12-20 00:33:31 UTC
Permalink
Post by Toolman Tim
|
|| I've just had a very strange problem after installing a webcam driver.
|| Upon completion the driver required a reboot, so off it all went. When
|| the machine came back up XP appeared to be booting OK, but then stopped
|| and went in to a boot loop. Upon closer inspection it seems there is a
|| blue screen with an error message appearing, but it flashes up way too
|| fast for me to read before it starts to reboot again and I'm not sure
|| how to turn the auto-reboot off in order to read it. BIOS somewhere,
| maybe?
|<snipped>
I forgot to mention that the "restart after error" is part of XP and is one
of the first things to turn off when you get running again. Right-click "My
Computer" select "Properties", click on the "Advanced" tab and look for
"Startup and recovery" - click on settings there. Find "Automatically
restart" and turn that off.
Thanks. Is there any way to do this without actually being in that XP
install? Can I change a setting on that drive when it's slaved from my
new install somehow?

Lee.
Toolman Tim
2004-12-20 01:16:10 UTC
Permalink
"***@DVDDebate" <***@dvddebate.com> wrote in message news:Q6pxd.6494$***@fe65.usenetserver.com...
| Toolman Tim wrote:
| > "Toolman Tim" <***@my.email.is.invalid> wrote in message
| > news:eP4xd.21055$***@fe05.lga...
| > |
| > | "***@DVDDebate" <***@dvddebate.com> wrote in message
| > | news:mx4xd.42311$***@fe41.usenetserver.com...
| > || I've just had a very strange problem after installing a webcam
driver.
| > || Upon completion the driver required a reboot, so off it all went.
When
| > || the machine came back up XP appeared to be booting OK, but then
stopped
| > || and went in to a boot loop. Upon closer inspection it seems there is
a
| > || blue screen with an error message appearing, but it flashes up way
too
| > || fast for me to read before it starts to reboot again and I'm not sure
| > || how to turn the auto-reboot off in order to read it. BIOS somewhere,
| > | maybe?
| > |<snipped>
| >
| > I forgot to mention that the "restart after error" is part of XP and is
one
| > of the first things to turn off when you get running again. Right-click
"My
| > Computer" select "Properties", click on the "Advanced" tab and look for
| > "Startup and recovery" - click on settings there. Find "Automatically
| > restart" and turn that off.
| >
| >
| Thanks. Is there any way to do this without actually being in that XP
| install? Can I change a setting on that drive when it's slaved from my
| new install somehow?
|
Wow - tough question...I'd usually say no, but someone may have better
information on editing an XP registry off of the non-booting drive. Plus
there's the issue of locating which reg key needs to be altered...
Toolman Tim
2004-12-20 01:43:24 UTC
Permalink
"Toolman Tim" <***@my.email.is.invalid> wrote in message news:JRpxd.26765$_%***@fe05.lga...
|
| "***@DVDDebate" <***@dvddebate.com> wrote in message
| news:Q6pxd.6494$***@fe65.usenetserver.com...
|| Toolman Tim wrote:
|| > "Toolman Tim" <***@my.email.is.invalid> wrote in message
|| > news:eP4xd.21055$***@fe05.lga...
|| > |
|| > | "***@DVDDebate" <***@dvddebate.com> wrote in message
|| > | news:mx4xd.42311$***@fe41.usenetserver.com...
|| > || I've just had a very strange problem after installing a webcam
| driver.
|| > || Upon completion the driver required a reboot, so off it all went.
| When
|| > || the machine came back up XP appeared to be booting OK, but then
| stopped
|| > || and went in to a boot loop. Upon closer inspection it seems there is
| a
|| > || blue screen with an error message appearing, but it flashes up way
| too
|| > || fast for me to read before it starts to reboot again and I'm not
sure
|| > || how to turn the auto-reboot off in order to read it. BIOS somewhere,
|| > | maybe?
|| > |<snipped>
|| >
|| > I forgot to mention that the "restart after error" is part of XP and is
| one
|| > of the first things to turn off when you get running again. Right-click
| "My
|| > Computer" select "Properties", click on the "Advanced" tab and look for
|| > "Startup and recovery" - click on settings there. Find "Automatically
|| > restart" and turn that off.
|| >
|| >
|| Thanks. Is there any way to do this without actually being in that XP
|| install? Can I change a setting on that drive when it's slaved from my
|| new install somehow?
||
| Wow - tough question...I'd usually say no, but someone may have better
| information on editing an XP registry off of the non-booting drive. Plus
| there's the issue of locating which reg key needs to be altered...
|
Okay - I *think* this is the registry key that needs to be changed to stop
the auto restart on error:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl]
"AutoReboot"=dword:00000001

Change the value of dword to 0 (dword:00000000)

But of course, if someone can't help you get to the registry on the F:
drive, it won't help much <g>
WinGuy
2004-12-19 10:16:18 UTC
Permalink
Hi, Lee. Using Windows Explorer (not Internet Explorer!) click on Tools |
Folder Options | View and make sure that "Show hidden files and folders" is
selected, that "Hide extensions for known file types" is not selected, and
that "Hide protected operating system files (Recommended)" is not selected.
Boot to the new HDD you said (in a later post than is quoted here) that you
created, so you can see the problem drive as a slave drive. Rename the
boot.ini file on that problem slave drive, and copy the boot.ini file from
the root of your new drive that works over to the root of the old problem
drive. Then see if the problem drive will now boot, at least into Safe Mode.
If so, do a repair (uh, upgrade) reinstall of XP onto the problem drive but
make sure you use the same exact CD that was used to originally install to
XP onto the problem HDD, else you might get locked out immediately following
the "repair" install. Not just any XP CD will work, it has to be the one
that was used to do the very 1st original XP install onto that problem HDD
(piracy protection issue).

If you can boot the XP CD and enter the Recovery Console, and while in that
RC you can see the problem HDD when it is the *boot* drive, then ONLY if you
are still having boot problems after trying the above then try this from the
command prompt in RC:
-----
Boot to Recovery Console from CD. It's assumed here that the CD drive is
drive d:
Be at root of Drive C.
Type these (answer y to over-write if asked)
copy d:\i386\ntldr
copy d:\i386\ntdetect.com
-----

Best wishes
Winguy
Post by ***@DVDDebate
I've just had a very strange problem after installing a webcam driver.
Upon completion the driver required a reboot, so off it all went. When the
machine came back up XP appeared to be booting OK, but then stopped and
went in to a boot loop. Upon closer inspection it seems there is a blue
screen with an error message appearing, but it flashes up way too fast for
me to read before it starts to reboot again and I'm not sure how to turn
the auto-reboot off in order to read it. BIOS somewhere, maybe?
Anyway, I tried booting to safe mode with no joy, then decided to
reinstall XP. XP install disc gets to the 'choose your drive to install
to' page and it lists my C drive but with no file system listed. Other
drives in the machine all show as NTFS. Odd, and not a little worrying. Is
the drive trashed, I wonder?
I spend a few minutes switching drives and jumpers around and eventually
get XP up and running on a whole new drive. My old drive is now slaved as
F: and, lo and behold, XP can see it fine and has identified it as having
an NTFS file system with all the files are still there and in working
order. A disc scan shows no errors on the disc.
Odd. So I switch everything back and try to boot from the old drive again.
No luck. Try XP install again and once more the install routine says there
is no file system on that drive.
I switch again, thinking I can just get the install app to re-install XP
on to the drive when it shows up as F:.
Still no good. Even when slaved, the XP install disc cannot find a file
system and insists that if I want XP on that drive it will need to be
completely reformatted. Which, considering it's a 100Gb drive with only 2%
space left, I'm not really that keen to do.
I'm now completely stumped. Can anybody offer any suggestions as to what
to try next?
Thanks,
Lee.
Lee@DVDDebate
2004-12-20 01:43:45 UTC
Permalink
Post by WinGuy
Hi, Lee. Using Windows Explorer (not Internet Explorer!) click on Tools |
Folder Options | View and make sure that "Show hidden files and folders" is
selected, that "Hide extensions for known file types" is not selected, and
that "Hide protected operating system files (Recommended)" is not selected.
Boot to the new HDD you said (in a later post than is quoted here) that you
created, so you can see the problem drive as a slave drive. Rename the
boot.ini file on that problem slave drive, and copy the boot.ini file from
the root of your new drive that works over to the root of the old problem
drive. Then see if the problem drive will now boot, at least into Safe Mode.
If so, do a repair (uh, upgrade) reinstall of XP onto the problem drive but
make sure you use the same exact CD that was used to originally install to
XP onto the problem HDD, else you might get locked out immediately following
the "repair" install. Not just any XP CD will work, it has to be the one
that was used to do the very 1st original XP install onto that problem HDD
(piracy protection issue).
Thanks for the helpful suggestions, Winguy, much appreciated. I checked
the boot.ini on both installs and they're identical. I've also looked
for files that changed at the time of the driver install but I can't
find anything suspicious other than _delis32.ini. I've renamed that and
tried to reboot, but still no luck.

I've also updated the BIOS of the motherboard with no effect.

Booting in to safe mode tells me that everything loads fine up to
agp440.sys. Is there a log file written on bootup that I can look at to
see what it fails to load?

Lee.
WinGuy
2004-12-20 03:54:18 UTC
Permalink
"***@DVDDebate" <***@dvddebate.com> wrote in message news:T8qxd.858$***@fe78.usenetserver.com...
...
Post by ***@DVDDebate
Thanks for the helpful suggestions, Winguy, much appreciated. I checked
the boot.ini on both installs and they're identical.
Ok. I've seen virus remove the path to windows folder from boot.ini,
although the system usually just complains and finds the windows folder
anyway and boots.
Post by ***@DVDDebate
I've also looked for files that changed at the time of the driver install
but I can't find anything suspicious other than _delis32.ini. I've renamed
that and tried to reboot, but still no luck.
Rename it back, just in case. I'm not sure, but I think it's part of Install
Shield.
Post by ***@DVDDebate
I've also updated the BIOS of the motherboard with no effect.
Booting in to safe mode tells me that everything loads fine up to
agp440.sys. Is there a log file written on bootup that I can look at to
see what it fails to load?
Aah, I think that's to do with your graphics card in the brown AGP
motherboard slot. In the menu that you can get to Safe Mode, do you have an
option to force VGA mode? That's only 640x480 16 colors. If that works but
the normal 800x600 Safe Mode will not boot then you might have a bad
graphics card driver or a physically bad card. Try reseating the card (first
be sure the AC Power cord is physically disconencted), if it's not built
onto the motherboard chipset.

Look for "ntbtlog.txt" in your windows or winnt folder. Might want to clear
it of old content before doing the boot attempt. Not all things that it says
it did not load are a problem. Usually, the culprit will be the last line or
maybe no more than one of the last 3 lines identifying a driver that is
causing a problem when the system won't boot.

Winguy
Lee@DVDDebate
2004-12-20 10:02:30 UTC
Permalink
Post by WinGuy
Post by ***@DVDDebate
I've also updated the BIOS of the motherboard with no effect.
Booting in to safe mode tells me that everything loads fine up to
agp440.sys. Is there a log file written on bootup that I can look at to
see what it fails to load?
Aah, I think that's to do with your graphics card in the brown AGP
motherboard slot. In the menu that you can get to Safe Mode, do you have an
option to force VGA mode? That's only 640x480 16 colors. If that works but
the normal 800x600 Safe Mode will not boot then you might have a bad
graphics card driver or a physically bad card. Try reseating the card (first
be sure the AC Power cord is physically disconencted), if it's not built
onto the motherboard chipset.
Graphics are on board, so no AGP card.
Post by WinGuy
Look for "ntbtlog.txt" in your windows or winnt folder. Might want to clear
it of old content before doing the boot attempt. Not all things that it says
it did not load are a problem. Usually, the culprit will be the last line or
maybe no more than one of the last 3 lines identifying a driver that is
causing a problem when the system won't boot.
Something you said earlier got me thinking last night. The machine is
a work machine and came with XP Pro already loaded. The XP install
disc I was using is not the same one that was originally installed. I
wonder if this might be the reason for it not showing up when I try to
repair it? Would the install disc refuse to acknowledge the existing
install if the discs were different? It's unlikely our support guys
will be able to tell which was the original. May even have been an OEM
install.

I'll check the ntblog later today, but to be honest I'm at the stage
now where I'm thinking I'll have to re-install a new drive and slave
this old one permanently :(

Lee.
--
Founder, DVD Debate
http://www.dvddebate.com
lee at dvddebate dot com

If you told a joke and someone died laughing, could you be found guilty of a mans laughter?
doS
2004-12-20 11:48:17 UTC
Permalink
refomat the old drive and reinstall xp.
Post by ***@DVDDebate
Post by WinGuy
Post by ***@DVDDebate
I've also updated the BIOS of the motherboard with no effect.
Booting in to safe mode tells me that everything loads fine up to
agp440.sys. Is there a log file written on bootup that I can look at to
see what it fails to load?
Aah, I think that's to do with your graphics card in the brown AGP
motherboard slot. In the menu that you can get to Safe Mode, do you have an
option to force VGA mode? That's only 640x480 16 colors. If that works but
the normal 800x600 Safe Mode will not boot then you might have a bad
graphics card driver or a physically bad card. Try reseating the card (first
be sure the AC Power cord is physically disconencted), if it's not built
onto the motherboard chipset.
Graphics are on board, so no AGP card.
Post by WinGuy
Look for "ntbtlog.txt" in your windows or winnt folder. Might want to clear
it of old content before doing the boot attempt. Not all things that it says
it did not load are a problem. Usually, the culprit will be the last line or
maybe no more than one of the last 3 lines identifying a driver that is
causing a problem when the system won't boot.
Something you said earlier got me thinking last night. The machine is
a work machine and came with XP Pro already loaded. The XP install
disc I was using is not the same one that was originally installed. I
wonder if this might be the reason for it not showing up when I try to
repair it? Would the install disc refuse to acknowledge the existing
install if the discs were different? It's unlikely our support guys
will be able to tell which was the original. May even have been an OEM
install.
I'll check the ntblog later today, but to be honest I'm at the stage
now where I'm thinking I'll have to re-install a new drive and slave
this old one permanently :(
Lee.
--
Founder, DVD Debate
http://www.dvddebate.com
lee at dvddebate dot com
If you told a joke and someone died laughing, could you be found guilty of a mans laughter?
Lee@DVDDebate
2004-12-20 11:56:32 UTC
Permalink
On Mon, 20 Dec 2004 06:48:17 -0500, "doS"
Post by doS
refomat the old drive and reinstall xp.
OK...and the 100Gb+ of data on there? How does your suggestion let me
keep that?

Lee.
--
Founder, DVD Debate
http://www.dvddebate.com
lee at dvddebate dot com

If you told a joke and someone died laughing, could you be found guilty of a mans laughter?
WinGuy
2004-12-20 13:40:40 UTC
Permalink
Post by ***@DVDDebate
Graphics are on board, so no AGP card.
In my last message I meant 256 colors in forced VGA mode, not 16. But you
are using a AGP driver. Try this... make a backup copy of the existing
Drivers folder, the one I mean is in the system32 folder. Then move these
files over from that HDD driver folder that does boot, and give it a try. I
guess you could not get into Safe Mode after selecting the VGA mode at the
menu?

atapi.sys
intelide.sys
pciidex.sys
storprop.dll
Post by ***@DVDDebate
Something you said earlier got me thinking last night. The machine is
a work machine and came with XP Pro already loaded. The XP install
disc I was using is not the same one that was originally installed. I
wonder if this might be the reason for it not showing up when I try to
repair it? Would the install disc refuse to acknowledge the existing
install if the discs were different? It's unlikely our support guys
will be able to tell which was the original. May even have been an OEM
install.
Not necessarily, since you didn't get a lockout at registration time. You
can upgrade a non pirated XP-H or XP-P, OEM or not, with the full (not an
upgrade) retail version of XP-P. Other combinations might result in lockout
at registration time, or simply refuse to install. If I remember correctly,
you said the install did not complete but errored at some point and went
into infinite reboot? It really sounds like it choked on a driver, and I'm
betting one of the above 4 that I listed, or a graphics driver.
Post by ***@DVDDebate
I'll check the ntblog later today, but to be honest I'm at the stage
now where I'm thinking I'll have to re-install a new drive and slave
this old one permanently :(
Don't give up just yet! Since you can access it as a slave, be sure to have
checked it for bad sectors too (it will take forever, I know, but do it). At
least you can back it up (theoretically) and the data there is still
availalbe. So is its registry still intact, I'll bet. Just some stupid
driver. You could also try backing up its current system32\drivers folder
and moving the entire one over from the drive that does boot. If that works,
or it then has entirely different problems, then a repair reinstall of XP
will probably fix it at that point. In that case it's probably a corrupt
graphics driver it's choking on right now, I guess.

Winguy
WinGuy
2004-12-20 14:36:09 UTC
Permalink
Lee, something else could be at issue here, especially if the old drive is
compressed. You said you have around 100gigs of existing programs and data
along with windows files on the problem drive. XP is going to need quite a
bit of space to backup your existing windows related files when you try to
install it over top of itself, and there is that 120gig limitation that
requires a registry mod for bigger HDDs to be recognized in their full
capacity, with warning from HDD manufactures that big HDD's formatted
without that mod can have data loss (or if SCSI, then a controller that can
recognize drivers bigger than 120gigs is required). So if that drive is over
120gigs, be aware.

Sooo! Move all the user data files that you can over to another drive, free
up as much room as you can without impacting actual programs or windows
files. Try to have at least 30 gigs free (that should be over kill, I'd
think). Then make sure you've checked the drive for bad sectors and also let
it automatically fix problems, and then try the re-install of XP-Pro again.
But if the drive is partitioned for greater than 120gigs, then after you
make as much room as possible then do an image copy of it to another drive
before you try the windows repair reinstall (upgrade), and then repartition
it into multiple drives that have no partition greater than 120gigs. Then
image the original content back and try the XP-Pro repair reinstall again.
You could then apply the "big drive" registry patch and do the image musical
chairs thing again to get the drive recognized as one drive and with
everything on it, finially.
WinGuy
2004-12-20 15:31:29 UTC
Permalink
Post by WinGuy
Lee, something else could be at issue here
...

Oh, and I forgot to (re)mention something very important, Lee. Whenever you
use the Maxtor or Western Digital (WD) utility to image a drive, after the
image and before you try to boot the new imaged drive be absolutely sure to
run a check for bad sectors and have it automatically fix problems too
before you boot the new imaged drive! The reason is that I've learned via
BSOD of that necessity the hard way, more than once, and I honestly stand by
that requirement. Only then configure to boot the new imaged drive and try
to reinstall XP over top of itself. Also, Office 10 will almost surely have
to be reinstalled if you're using it (I don't know why, but it's happened
many times to me). Don't let XP partition the drive, use the HDD utility
that came with the drive to do that, after you've made a backup image of its
content.

Winguy
Migak the clitoris-beautifier
2004-12-20 12:29:14 UTC
Permalink
Post by WinGuy
If so, do a repair (uh, upgrade) reinstall of XP
onto the problem drive but make sure you use the same exact CD that was
used to originally install to XP onto the problem HDD, else you might get
locked out immediately following the "repair" install. Not just any XP CD
will work, it has to be the one that was used to do the very 1st original
XP install onto that problem HDD (piracy protection issue).
<*blink*> BWAHAHAHAHAHAHAH!!! *CHOKE* *GURGLE* *CHOKE* *COUGH* *SPLUTTER*
*WHEEZE*

24hoursupport.helpdesk, microsoft.public.windowsxp.help_and_support,
microsoft.public.windowsxp.general

BWAHAHAHAHAHAH!! Fucking retards.
--
Registered Linux User: #344402
Akhenaten: Registered Linux Machine: #235500
2.6.8.1-12-i686-smp Dual i686 Intel(R) Xeon(TM) CPU 2.80GHz GNU/Linux
Chief Justice Baiden Trotforth-Guffingtot
2004-12-20 12:30:53 UTC
Permalink
Post by WinGuy
If so, do a repair (uh, upgrade) reinstall of XP
onto the problem drive but make sure you use the same exact CD that was
used to originally install to XP onto the problem HDD, else you might get
locked out immediately following the "repair" install. Not just any XP CD
will work, it has to be the one that was used to do the very 1st original
XP install onto that problem HDD (piracy protection issue).
<*blink*> BWAHAHAHAHAHAHAH!!! *CHOKE* *GURGLE* *CHOKE* *COUGH* *SPLUTTER*
*WHEEZE*

24hoursupport.helpdesk, microsoft.public.windowsxp.help_and_support,
microsoft.public.windowsxp.general

BWAHAHAHAHAHAH!! Fucking retards.
--
Registered Linux User: #344402
Akhenaten: Registered Linux Machine: #235500
2.6.8.1-12-i686-smp Dual i686 Intel(R) Xeon(TM) CPU 2.80GHz GNU/Linux
Chief Ohara
2004-12-20 12:46:00 UTC
Permalink
"Chief Justice Baiden Trotforth-Guffingtot"
Post by WinGuy
If so, do a repair (uh, upgrade) reinstall of XP
onto the problem drive but make sure you use the same exact CD that was
used to originally install to XP onto the problem HDD, else you might get
locked out immediately following the "repair" install. Not just any XP CD
will work
<snip>
LOL
chopsaw
2004-12-22 04:17:38 UTC
Permalink
if the xp disk is saying you have no file system I know of 2
posibilities:

1: you are using a RAID controller and need to hit f6 when booting off
the cd to install the 3rd party driver

2: you have used a program that has changed the file system on the
frive such as GoBack.

Michael Cecil
2004-12-20 11:56:13 UTC
Permalink
Post by ***@DVDDebate
I've just had a very strange problem after installing a webcam driver.
Upon completion the driver required a reboot, so off it all went. When
the machine came back up XP appeared to be booting OK, but then stopped
and went in to a boot loop. Upon closer inspection it seems there is a
blue screen with an error message appearing, but it flashes up way too
fast for me to read before it starts to reboot again and I'm not sure
how to turn the auto-reboot off in order to read it. BIOS somewhere, maybe?
Anyway, I tried booting to safe mode with no joy, then decided to
reinstall XP.
You never got the menu where you could choose Safe Mode? BTW, I'd have
tried Last Known Good Configuration before Safe Mode or reformatting.
It's how you can usually get back to where you were before installing new
drivers.
Post by ***@DVDDebate
XP install disc gets to the 'choose your drive to install
to' page and it lists my C drive but with no file system listed. Other
drives in the machine all show as NTFS. Odd, and not a little worrying.
Is the drive trashed, I wonder?
Not the entire drive but it sounds like the partition table is corrupt.
You can recover it in-place with some products like DiskPatch from
http://diydatarecovery.nl. I think Acronis RecoveryExpert will do
in-place recoveries too. No doubt there are other products as well.
--
Michael Cecil
http://home.comcast.net/~macecil/
Yilak the walrus-apologiser
2004-12-20 12:08:04 UTC
Permalink
Post by Michael Cecil
BTW, I'd have
tried Last Known Good Configuration before Safe Mode or reformatting.
Fat lump of fucking good that's going to do him now, eh, cuntfungus.
--
Registered Linux User: #344402
Akhenaten: Registered Linux Machine: #235500
2.6.8.1-12-i686-smp Dual i686 Intel(R) Xeon(TM) CPU 2.80GHz GNU/Linux
Lee@DVDDebate
2004-12-20 12:20:21 UTC
Permalink
Post by Michael Cecil
Post by ***@DVDDebate
I've just had a very strange problem after installing a webcam driver.
Upon completion the driver required a reboot, so off it all went. When
the machine came back up XP appeared to be booting OK, but then stopped
and went in to a boot loop. Upon closer inspection it seems there is a
blue screen with an error message appearing, but it flashes up way too
fast for me to read before it starts to reboot again and I'm not sure
how to turn the auto-reboot off in order to read it. BIOS somewhere, maybe?
Anyway, I tried booting to safe mode with no joy, then decided to
reinstall XP.
You never got the menu where you could choose Safe Mode?
Er..yes, like I said in the line above, I tried booting to safe mode,
but it did exactly the same thing.
Post by Michael Cecil
BTW, I'd have
tried Last Known Good Configuration before Safe Mode or reformatting.
It's how you can usually get back to where you were before installing new
drivers.
I did, but I thought it too obvious to mention.
Post by Michael Cecil
Post by ***@DVDDebate
XP install disc gets to the 'choose your drive to install
to' page and it lists my C drive but with no file system listed. Other
drives in the machine all show as NTFS. Odd, and not a little worrying.
Is the drive trashed, I wonder?
Not the entire drive but it sounds like the partition table is corrupt.
You can recover it in-place with some products like DiskPatch from
http://diydatarecovery.nl. I think Acronis RecoveryExpert will do
in-place recoveries too. No doubt there are other products as well.
Would a damaged partition table still allow the drive to be visible
and perfectly working as a slave to another OS? While slaved, the
drive also passed a disc check under XP with no errors.

Lee.
--
Founder, DVD Debate
http://www.dvddebate.com
lee at dvddebate dot com

If you told a joke and someone died laughing, could you be found guilty of a mans laughter?
Billy
2004-12-20 18:23:15 UTC
Permalink
Post by ***@DVDDebate
Post by Michael Cecil
Post by ***@DVDDebate
I've just had a very strange problem after installing a webcam driver.
Upon completion the driver required a reboot, so off it all went. When
the machine came back up XP appeared to be booting OK, but then stopped
and went in to a boot loop. Upon closer inspection it seems there is a
blue screen with an error message appearing, but it flashes up way too
fast for me to read before it starts to reboot again and I'm not sure
how to turn the auto-reboot off in order to read it. BIOS somewhere, maybe?
Anyway, I tried booting to safe mode with no joy, then decided to
reinstall XP.
You never got the menu where you could choose Safe Mode?
Er..yes, like I said in the line above, I tried booting to safe mode,
but it did exactly the same thing.
Post by Michael Cecil
BTW, I'd have
tried Last Known Good Configuration before Safe Mode or reformatting.
It's how you can usually get back to where you were before installing new
drivers.
I did, but I thought it too obvious to mention.
Post by Michael Cecil
Post by ***@DVDDebate
XP install disc gets to the 'choose your drive to install
to' page and it lists my C drive but with no file system listed. Other
drives in the machine all show as NTFS. Odd, and not a little worrying.
Is the drive trashed, I wonder?
Not the entire drive but it sounds like the partition table is corrupt.
You can recover it in-place with some products like DiskPatch from
http://diydatarecovery.nl. I think Acronis RecoveryExpert will do
in-place recoveries too. No doubt there are other products as well.
Would a damaged partition table still allow the drive to be visible
and perfectly working as a slave to another OS? While slaved, the
drive also passed a disc check under XP with no errors.
But did you do the Recovery Console Chkdsk /R for that drive, why not?
Continue reading on narkive:
Loading...