Damn... fresh new install then, huh? The one which gives
strong warnings of puting two operating systems on the same
partition? It's probably stupid to ask, but how likely am I
to lose all of the data on that HDD if this option is selected?
-----Original Message-----
If the second repair option doesn't work then the old
installation is rooted
and must be completely removed.
--
sqr
--
ftp://sqr.myftp.biz
Allow me to re-itterate. At boot from the WinXP CD, it
gives three options: Setup WinXP, Start the repair console,
and exit (f3). On choosing the first option, it
automaticaly checks for prior-installment windows OS's, and
finds mine already there. From there, it gives another
three options: Allow setup to attempt a repair of the
installed OS (already did that... it lead to my current
situation), install a fresh version of WinXP (gives a
warning about installing two seperate OS's on the same
partition, implying that it won't be simply overwriting the
current OS... there is no space for another partition,
btw), and quiting the setup program.
Now, when I originally allowed for the setup program to
"attempt to repair" my installment of WinXP, I came to the
situation of my computer continually booting into setup
(irregardless of the presence of the CD), and not seeing
ANY input devices. Also, the message "Files Needed. The
file 'asms' on Windows XP Home Edition CD-ROM is needed.
Type the path where the filr is located, and then click
OK." Of course, the latter message means it doesn't see the
CD-ROM, but it doesn't see ANY other input device,
including my keyboard. Also, booting into safe mode doesn't
help: the message "Setup cannot run in safe mode" is
presented, and I again find I am unable to use any of my
input devices.
Assuming you respond to this message, I appologize for
creating multiple posts, but I was trying to ensure that my
message was responded to. Specifically, this is directed
towards "Old Geek."
-----Original Message-----
As far as actually running setup is
concerned, there's only one place where I can do that:
booting from the CD.
Wrong, you can install window with the dos installer after
you boot from a
win9X which has
cd-rom and smartdrive support.
In which case, the only option is to
install a fresh version of Windows XP Home Edition
You must take the second repair option not the first.
--
sqr
--
ftp://sqr.myftp.biz
Continuing on...
Well, boot.ini isn't redirecting windows towards the
setup.
Here's the command string result:
C:\>type boot.ini
[boot loader]
timeout=1
default=multi(0)disk(0)rdisk(0)partition(1)\windows
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft
Windows XP Home Edition"/fastdetect
And about rerunning the setup: I never really
initiated it,
I only ran the repair process on the already existing
Windows XP system. As far as actually running setup is
concerned, there's only one place where I can do that:
booting from the CD. In which case, the only option is to
install a fresh version of Windows XP Home Edition.
It also
gives a warning that it's not recommended to install two
OS's onthe same partition, implying that this would do
little more than create more problems, so I'll save
that as
a last resort.
Original thread:
I would try to get to the boot.ini file thru the recovery
console and
see if it is directing it to boot to setup. if it is,
change it and
see what happens.
Of course if setup didn't finish and things are missing
that won't do
much good.
maybe rerunning the setup will help.
On Thu, 4 Dec 2003 16:14:21 -0800, "Eqlipse"
<
[email protected]>
wrote:
Since no one replied to what I said earlier, I'll just
repost a summarized version, along with what was written
earlier...
Setup continually restarts, irregardless of whether
or not
the CD is in there. Considering I never actually ran
setup,
but only booted from the Windows XP Home Edition CD to
allow it to repair a certain problem on my computer
(which
it did and then rebooted), that would be problem number
one. Problem number two would be the fact that it
shows the
"file 'asms' on Windows XP Home Edition CD-ROM is
needed"
message, which means that it doesn't see the CD-Rom.
Okay,
no biggie... except that it doesn't see ANY input
devices,
including keyboard and mouse. It also will not allow
me to
boot into safe mode since "Setup cannot run in safe
mode."
Here's the original postings:
Okay, I wasn't very clear before. IT DOES NOT BOOT.
If you
read more carefully, attempting to boot into safe
mode only
halts the system because "setup cannot run in safe
mode."
And none of the input devices are being read by "setup,"
which, by the way, boots with the first three steps
already
completed and offers no options for setup.
The driver issue was already cleared with the
reinstalling
of the windows drivers through the setup program. In
other
words, the drivers are not the problem right now:
it's the
setup program starting up all on its own without even
offering any options to it, irregardless of wether
or not
the CD is in the drive. This is interesting considerng I
told setup to repair a currently existing
installation, not
to create a new one.
Again, just to be clear: the drivers are not the
problem,
but merely where this all started. The problem right
now is
the setup program runnin on its own accord and
screwing up
royally.
-----Original Message-----
Boot the computer into safe mode if you can to
remove the
SB Live drivers.
When you have the system running again then disable or
remove what you can
in device manager eg.video, LAN drivers. When this
is done
then install the
SB Live drivers first.
If you perform a repair install be sure you select the
second repair option
as this will keep all of your setting and files.
The only
caveat is you must
reinstall all of your patches and updates.
--
sqr
--
ftp://sqr.myftp.biz
After installing some new drivers for my soundcard
(Creative Labs Live!), my computer failed to start.
Loading
it in safe mode such that I could see the boot
sequence, I
saw it was hanging on the "mup.sys" file. After
trying
several other boot options, all of which hanged
on that
particular file, I loaded my Windows XP Home Edition
CD and
booted from there.
First, I tinkered around with the recovery console,
looking
specifically at the bootcfg (boot configuration)
and the
processes being loaded. I didn't change/alter
anything, I
just looked at all the settings and processes, and
couldn't
find any discrepencies.
Next, I instead ventured to "setup Windows XP
now," the
first option on the CD's boot interface. From
there, it
automaticaly detected my current operating system,
and gave
the option to "Repair the selected Windows XP
installation". I already knew this option was there,
but I
prefer not to allow an automatic process run through
until
I have tried to fix something myself (I've been using
computers for over 17 years now, and prefer doing
things
myself). I let it run-through it's automatic
processes, and
reboot my system.
Now comes the interesting part, where I am at
right now:
irregardless of whether or not the CD is in the
drive, it
will automatically start the setup process. What's
more, it
shows the "The File 'Asms' on Windows XP Professional
CD-ROM Is Needed" error, which means it cannot
see the
CD-ROM... which would not be such a great problem,
except
it can't see ANY devices, including my keyboard and
mouse,
eventhough it seems to think they're there. It
didn't hang
at that point, it simply doesn't see/accept any
input from
any devices. And, irregargless of what boot options
selected (or even new ones created through the
recovery
console), it will start Windows XP Home Edition
Setup...
even in safe mode, which it tells me ic can't do,
and to
restart (in which case it's apparent that even
through that
boot sequence, it still cannot read any input
devices).
Now, before I completely install a fresh new copy of
Windows XP on my primary hard drive and risk losing
all of
the valuable work I had on it, I would much like
some other
alternatives.
Thank you.
.
.
.
.
.
