Can't install Vista

  • Thread starter Thread starter Jan :\)
  • Start date Start date
The media I have has both the x64 and x86 (32) on it and I am given the
choice at the time of install.

Jan, if I may ask where have you come up with media with both x64 and x86 on
the same media? I know that retail copies are separate dvds for x86 and x64
and the user is not offered such an option. I wouldn't mind having such a
thing if you don't mind sharing what channel is providing it.
 
Ok.....after several attempts to install, and a number of hours of
troubleshooting, I finally found the culprit. It was my Antec external hard
drive.

Apparently, I discovered this after I unplugged all but the one drive in the
machine that I wanted to install the Vista on and still got the error. This
really confused me, even more than usual. I needed information that was
backed up on the external hard drive which is normally plugged into the
machine, so I unplugged it the machine to use on another. While the other
machine was retrieving the data, I tried the install again and Bingo!! It
began the install and completed normally. I spent the rest of the day
setting things up again, and the next morning installed all the necessary
drivers and updates and programs and such.

Yesterday, I moved the external drive back to the home machine so that I
could do a backup of the new install, and all went fine until I later
installed a new program that requires a reboot> Sur-prise, Sur-prise!!!
When it came back up I got the Operating system can not be found. Gah!!!!
GRRRRR!! So....I tried to do a repair using the Vista media DVD and it
would not repair, and I could not reinstall as I got the original error. At
this point I was totally confused. But....then I remembered something I saw
when it first booted up with the DVD, that there was one drive that was
listed apart from the others as it went through the boot setup.
Hmmmm......why was that drive out there like that, which I had not seen
before, and which one was it? There should have been only one drive there,
outside of the CD/DVD ROM and the floppy that were still plugged in. So I
booted up and went to the BIOS. It seems somehow the external drive was
listed after the floppy and CD/DVD ROM.

I decided to do a little test, and turned off the external drive, then
rebooted. Voila!! It booted into the Vista and everything was still
there!! Whooo hooo!! To back up my suspicion on the external drive, I turned
it back on and then rebooted. Again, "Operating system not fond" AHA!!

Now I was pretty sure I had the culprit nailed, so I went to the BIOS,
changed the lineup of the drives, putting the drive with the Vista in line
after the floppy and CD/DVD ROM, as it was the only one with a operating
system. Rebooted and all came back up, booted into Vista as it should. Then
to further test, turned the external drive back on, and rebooted. Again, it
booted into Vista as it should, and I have had several more reboots as I
have installed more programs and updates. So.....I may have left out a few
things, but, that seems to have been the primary problem with the install.
I just recently got the external hard drive, and this is my first time doing
an install with it. So now I know to turn it off/unplug it when I am doing
an install.

This was at least the cause of my problem, and I wanted to pass on what I
discovered in case it might help someone else.

Thank you all for your time and help. It was very much appreciated, and it
kept me plugging at it until I was able to nail the guilty party and get it
resolved. :-)

Jan :)
 
MSDN and TechNet both make this kind of media available in their
subscriptions. As a Microsoft MVP I am surprised that you are not not only
aware of this, but, also have access to such media.

Jan :)
 
Ok.....after several attempts to install, and a number of hours of
troubleshooting, I finally found the culprit. It was my Antec external hard
drive.

Thank you all for your time and help. It was very much appreciated, and it
kept me plugging at it until I was able to nail the guilty party and get it
resolved. :-)

The guilty party is actually Microsoft, no surprise. I had a similar
experience. It seems that external drives especially if they are setup
as external ESATA can confuse Vista, even XP, probably because your
system didn't have a up today controller designed specifically for
Vista. So Vista being really, really stupid ends up trying to boot off
a non system disk, likely your external or just flat out refuses to
see the external unless and until your fool around with the order your
external drives are plugged into your MB or it might generate a Blue
Screen of Death, not booting at all.

Of course the moronic fanboy crowd with try to point their finger
exclusively at third party hardware makers. They always do. But
wait... AHCI specs were originally written way back in 2004! Long
before Vista was ever released.

Following is NOT an attempt to explain YOUR specific problem, rather
to expose Microsoft's way of doing business.

http://www.intel.com/technology/serialATA/index.htm

Learn more here:

http://en.wikipedia.org/wiki/Serial_ATA

Finally the wooden stake through the heart

http://www.answers.com/topic/advanced-host-controller-interface?cat=technology

Common problems switching to AHCI under Windows:

Enabling AHCI in a system BIOS will cause a 0x7B Blue Screen of Death
STOP error on installations of Windows XP where AHCI/RAID drivers for
that system's chipset are not installed. Switching to AHCI mode
requires installing new drivers before changing the BIOS settings.

When attempting to install Microsoft Windows XP or a previous version
on an AHCI-enabled system will cause the setup to fail with the error
message "set up could not detect hard disk drive...". This problem can
only be corrected by either using a floppy disk with the appropriate
drivers, by slipstreaming the appropriate drivers into the Windows XP
installation CD or by turning on IDE emulation in the BIOS settings if
available.

Enabling AHCI in a system BIOS with Windows Vista already installed
will result in a BSoD if SATA has been running in IDE mode during
Vista's installation. Before enabling AHCI in the BIOS, users must
first follow the instructions found at Microsoft Knowledge Base
article 922976.

Enabling AHCI in a system BIOS on installations of Windows XP or
Windows Vista, will cause SATA Optical drives to disappear. A Hotfix
for Windows Vista is available under the title: "SATA optical drives
are not available after you start a Windows Vista-based computer."[3]

Now why do I bring this all up? Simple. The Vista DVD COULD have and
should have come with a generic AHCI controller or minus that some
warning about ESATA drives and the problems you will likely run into.
But the idiots of Redmond said screw that... just like they said screw
making sure popular printers and scanners under Vista will support ALL
the features they did under XP.

Need proof? Check Adam Albright's revealing post documenting
confidential emails between various Microsoft big shots including
Ballmer that not only acknowledged these shortcoming, but try to hide
them... until it came out during Discovery during a court case.
Another reason Microsoft is often referred to as the Evil Empire.
They don't give a crap how much harm and grief they cause users by
taking shortcuts. In fact they go out of they way to get you to
upgrade to Vista allowing some MB makers to use a Vista Certified logo
when they got to know damn well the product was shipped without some
necessary drivers.

Of course the fanboy crowd rather bow down and blindly worship
Microsoft, no matter what facts get in the way that almost always
points to them being a big part of the problem.
 
Ringmaster wrote:

-----------------------------------

You're an idiot!

By PowerUser:
"Licentious. Obnoxious. Anti-democratic. In case you can't tell, I'm
making a direct reference to Mr. Adam Albright. Before I launch into my
main topic, I want to make a few matters crystal-clear: (1) Failure to
recognize this salient point will result in Adam's getting free reign to
enshrine irrational fears and fancies as truth, and (2) as a result of
that, my observations are perhaps unique. Now that you know where I
stand on those issues, I can safely say that wily cutthroats like Adam
are not born -- they are excreted. However unsavory that metaphor may
be, Adam acts as if he were King of the World. This hauteur is
astonishing, staggering, and mind-boggling. He truly believes that he
defends the real needs of the working class. It is just such
counter-productive megalomania, muddleheaded egoism, and intellectual
aberrancy that stirs Adam to carve out space in the mainstream for
ungrateful politics.

I want to draw two important conclusions from this. The first is that
Adam and his gofers are wolves in sheep's clothing who will create
profound emotional distress for people on both sides of the issue
eventually, and the second is that the justification he gave for seeking
to judge people by the color of their skin while ignoring the content of
their character was one of the most addlepated justifications I've ever
heard. It was so addlepated, in fact, that I will not repeat it here.
Even without hearing the details you can still see my point quite
clearly: Adam keeps telling everyone within earshot that honesty and
responsibility have no cash value and are therefore worthless. I'm
guessing that Adam read that on some Web site of dubious validity. More
reliable sources generally indicate that he isn't as smart as he thinks
he is. As an interesting experiment, try to point this out to
Adam. (You might want to don safety equipment first.) I think you'll
find that if he had even a shred of intellectual integrity, he'd admit
that he has no evidence or examples to back up his point. Still, I
recommend you check out some of his commentaries and draw your own
conclusions on the matter. Adam teaches workshops on clericalism.
Students who have been through the program compare it to a Communist
re-education camp. Those who fail to learn from history are doomed to
repeat it. Of course, if Adam had learned anything from history, he'd
know that I challenge him to point out any text in this letter that
proposes that we ought to worship feckless mountebanks as folk heroes.
It isn't there. There's neither a hint nor a suggestion of such a thing.


We no longer have the luxury of indulging in universalist, altruistic
principles that, no matter how noble they may appear, have enabled the
most self-satisfied spouters I've ever seen to compose paeans to
irrationalism. Didn't Adam tell his comrades that he wants to make
people suspicious of those who speak the truth? Did he first give any
thought to what would happen if he did? Of course, that question is
ridiculous -- as ridiculous as his gormless platitudes. None but the
grotesque can deny that he says that the sun rises just for him. What he
means by this, of course, is that he wants free reign to threaten the
existence of human life, perhaps all life on the planet. I understand
that I become truly impatient with people who refuse to recognize the
key role that he is playing in the destruction of our civilization, but
from the fog and mist of his disquisitions rises the leering grimace of
nihilism. An equal but opposite observation is that I and Adam part
company when it comes to the issue of quislingism. He feels that
those who disagree with him should be cast into the outer darkness,
should be shunned, should starve, while I suspect that he needs to stop
living in a fool's paradise. But there's the rub; his idea of mutinous
autism is no political belief. It is a fierce and burning gospel of
hatred and intolerance, of murder and destruction, and the unloosing of
an irascible blood-lust. It is, in every sense, a doctrinaire and pagan
religion that incites its worshipers to an infernal frenzy and then
prompts them to precipitate riots.


Adam does not merely undermine the current world order. He does so
consciously, deliberately, willfully, and methodically. His undertakings
were never about tolerance and equality. That was just window dressing
for the "innocents". Rather, someone has been giving Adam's brain a very
thorough washing, and now Adam is trying to do the same to us. Several
things he has said have brought me to the boiling point. The statement
of his that made the strongest impression on me, however, was something
to the effect of how he is a refined gentleman with the soundest
education and morals you can imagine. Forgive me for boring you with all
the gory details, but Adam's hypocrisy is transparent. Even the least
discerning among us can see right through it.


It's easy to tell if Adam's lying. If his lips are moving, he's lying.
Although Adam demonstrates a great deal of ignorance and presumption
when he says that he commands an army of robots that live in the hollow
center of the earth and produce earthquakes whenever they feel like
shaking things up a bit on the surface, the fact remains that in order
to convince us that he has the authority to issue licenses for
practicing heathenism, Adam often turns to the old propagandist trick of
comparing results brought about by entirely dissimilar causes. Now that
you've read the bulk of this letter, it should not come as a complete
surprise that there can be no argument that when I first realized that
Mr. Adam Albright is a proponent of "paternalism" -- a term Adam uses
catachrestically in place of "Pyrrhonism" -- a cold shudder ran down my
back. However, this fact bears repeating again and again, until the
words crack through the hardened exteriors of those who would violate
the basic tenets of journalism and scholarship. I am referring, of
course, to the likes of Adam Albright."

Want to read more about this failed drunken accountant and big mouth
lying pig?
For your reading pleasure!

http://groups.google.com/groups/profile?hl=en&enc_user=tYag3woAAABrYFiZuwWGCKzw8oMmJKS7

Enjoy!
I know I did!...LOL!
Frank
 
I generally don't discuss the MSDN downloads in the general ng, but yes I do
now about those. However, I was thinking in terms of licenses which permit
personal and productivity use, which MSDN (excepting one copy of Office)
would not. Sorry for my confusion.
 
I can't believe that I just saw the same exact thing yesterday!

The only thing I had done was install Windows Search 4.0. After the reboot
I got OS disk not found just like you describe. Both my optical drives and
internal hard drives had moved to the last four items in the boot menu (7
thru 10). I assume if a usb entry is ahead of those the boot will halt if a
usb hard drive is attached, which one was. I reordered the boot order so
the optical and hard drives were back in line after the floppy and moved on.

But I can't for the life of me figure out how the order got changed like
that. This is a six month old box and there has never been anything happen
on it like this. And the usb drive enclosure has been attached continuously
for the whole time.

I agree that usb drives should not be connected during installation or
upgrade of Windows and I have had a couple of enclosures that prevented a
boot or caused Windows Explorer to stop working, but I have never seen
anything change boot order settings like this.
 
I think it is the firmware in her enclosure. I have known since the
beginning of Longhorn beta that some enclosures were incompatible with
Vista. For a while Maxtor OneTouches were being reported a lot. I haven't
seen that with a Vantec enclosure like she has but there are some enclosures
that are fine with XP but play havoc with Vista. The answer is to buy Vista
certified enclosures and be prepared for older enclosures to work or not on
a case by case basis.

Ringmaster said:
Ok.....after several attempts to install, and a number of hours of
troubleshooting, I finally found the culprit. It was my Antec external
hard
drive.

Thank you all for your time and help. It was very much appreciated, and
it
kept me plugging at it until I was able to nail the guilty party and get
it
resolved. :-)

The guilty party is actually Microsoft, no surprise. I had a similar
experience. It seems that external drives especially if they are setup
as external ESATA can confuse Vista, even XP, probably because your
system didn't have a up today controller designed specifically for
Vista. So Vista being really, really stupid ends up trying to boot off
a non system disk, likely your external or just flat out refuses to
see the external unless and until your fool around with the order your
external drives are plugged into your MB or it might generate a Blue
Screen of Death, not booting at all.

Of course the moronic fanboy crowd with try to point their finger
exclusively at third party hardware makers. They always do. But
wait... AHCI specs were originally written way back in 2004! Long
before Vista was ever released.

Following is NOT an attempt to explain YOUR specific problem, rather
to expose Microsoft's way of doing business.

http://www.intel.com/technology/serialATA/index.htm

Learn more here:

http://en.wikipedia.org/wiki/Serial_ATA

Finally the wooden stake through the heart

http://www.answers.com/topic/advanced-host-controller-interface?cat=technology

Common problems switching to AHCI under Windows:

Enabling AHCI in a system BIOS will cause a 0x7B Blue Screen of Death
STOP error on installations of Windows XP where AHCI/RAID drivers for
that system's chipset are not installed. Switching to AHCI mode
requires installing new drivers before changing the BIOS settings.

When attempting to install Microsoft Windows XP or a previous version
on an AHCI-enabled system will cause the setup to fail with the error
message "set up could not detect hard disk drive...". This problem can
only be corrected by either using a floppy disk with the appropriate
drivers, by slipstreaming the appropriate drivers into the Windows XP
installation CD or by turning on IDE emulation in the BIOS settings if
available.

Enabling AHCI in a system BIOS with Windows Vista already installed
will result in a BSoD if SATA has been running in IDE mode during
Vista's installation. Before enabling AHCI in the BIOS, users must
first follow the instructions found at Microsoft Knowledge Base
article 922976.

Enabling AHCI in a system BIOS on installations of Windows XP or
Windows Vista, will cause SATA Optical drives to disappear. A Hotfix
for Windows Vista is available under the title: "SATA optical drives
are not available after you start a Windows Vista-based computer."[3]

Now why do I bring this all up? Simple. The Vista DVD COULD have and
should have come with a generic AHCI controller or minus that some
warning about ESATA drives and the problems you will likely run into.
But the idiots of Redmond said screw that... just like they said screw
making sure popular printers and scanners under Vista will support ALL
the features they did under XP.

Need proof? Check Adam Albright's revealing post documenting
confidential emails between various Microsoft big shots including
Ballmer that not only acknowledged these shortcoming, but try to hide
them... until it came out during Discovery during a court case.
Another reason Microsoft is often referred to as the Evil Empire.
They don't give a crap how much harm and grief they cause users by
taking shortcuts. In fact they go out of they way to get you to
upgrade to Vista allowing some MB makers to use a Vista Certified logo
when they got to know damn well the product was shipped without some
necessary drivers.

Of course the fanboy crowd rather bow down and blindly worship
Microsoft, no matter what facts get in the way that almost always
points to them being a big part of the problem.
 
No...it is not a 'Vantec', it is an Antec Veris MX-1.
http://www.antec.com/us/productDetails.php?ProdID=77150
The Drive is a Seagate, Barracuda SATA/300, 750 GB

The problem was in the BIOS....once that was corrected, the problem was
resolved.

Jan :)


Colin Barnhorst said:
I think it is the firmware in her enclosure. I have known since the
beginning of Longhorn beta that some enclosures were incompatible with
Vista. For a while Maxtor OneTouches were being reported a lot. I haven't
seen that with a Vantec enclosure like she has but there are some
enclosures that are fine with XP but play havoc with Vista. The answer is
to buy Vista certified enclosures and be prepared for older enclosures to
work or not on a case by case basis.

Ringmaster said:
Ok.....after several attempts to install, and a number of hours of
troubleshooting, I finally found the culprit. It was my Antec external
hard
drive.

Thank you all for your time and help. It was very much appreciated, and
it
kept me plugging at it until I was able to nail the guilty party and get
it
resolved. :-)

The guilty party is actually Microsoft, no surprise. I had a similar
experience. It seems that external drives especially if they are setup
as external ESATA can confuse Vista, even XP, probably because your
system didn't have a up today controller designed specifically for
Vista. So Vista being really, really stupid ends up trying to boot off
a non system disk, likely your external or just flat out refuses to
see the external unless and until your fool around with the order your
external drives are plugged into your MB or it might generate a Blue
Screen of Death, not booting at all.

Of course the moronic fanboy crowd with try to point their finger
exclusively at third party hardware makers. They always do. But
wait... AHCI specs were originally written way back in 2004! Long
before Vista was ever released.

Following is NOT an attempt to explain YOUR specific problem, rather
to expose Microsoft's way of doing business.

http://www.intel.com/technology/serialATA/index.htm

Learn more here:

http://en.wikipedia.org/wiki/Serial_ATA

Finally the wooden stake through the heart

http://www.answers.com/topic/advanced-host-controller-interface?cat=technology

Common problems switching to AHCI under Windows:

Enabling AHCI in a system BIOS will cause a 0x7B Blue Screen of Death
STOP error on installations of Windows XP where AHCI/RAID drivers for
that system's chipset are not installed. Switching to AHCI mode
requires installing new drivers before changing the BIOS settings.

When attempting to install Microsoft Windows XP or a previous version
on an AHCI-enabled system will cause the setup to fail with the error
message "set up could not detect hard disk drive...". This problem can
only be corrected by either using a floppy disk with the appropriate
drivers, by slipstreaming the appropriate drivers into the Windows XP
installation CD or by turning on IDE emulation in the BIOS settings if
available.

Enabling AHCI in a system BIOS with Windows Vista already installed
will result in a BSoD if SATA has been running in IDE mode during
Vista's installation. Before enabling AHCI in the BIOS, users must
first follow the instructions found at Microsoft Knowledge Base
article 922976.

Enabling AHCI in a system BIOS on installations of Windows XP or
Windows Vista, will cause SATA Optical drives to disappear. A Hotfix
for Windows Vista is available under the title: "SATA optical drives
are not available after you start a Windows Vista-based computer."[3]

Now why do I bring this all up? Simple. The Vista DVD COULD have and
should have come with a generic AHCI controller or minus that some
warning about ESATA drives and the problems you will likely run into.
But the idiots of Redmond said screw that... just like they said screw
making sure popular printers and scanners under Vista will support ALL
the features they did under XP.

Need proof? Check Adam Albright's revealing post documenting
confidential emails between various Microsoft big shots including
Ballmer that not only acknowledged these shortcoming, but try to hide
them... until it came out during Discovery during a court case.
Another reason Microsoft is often referred to as the Evil Empire.
They don't give a crap how much harm and grief they cause users by
taking shortcuts. In fact they go out of they way to get you to
upgrade to Vista allowing some MB makers to use a Vista Certified logo
when they got to know damn well the product was shipped without some
necessary drivers.

Of course the fanboy crowd rather bow down and blindly worship
Microsoft, no matter what facts get in the way that almost always
points to them being a big part of the problem.
 
No....the problem was with the BIOS....once that was corrected, the problem
was resolved.

Jan :)

Ringmaster said:
Ok.....after several attempts to install, and a number of hours of
troubleshooting, I finally found the culprit. It was my Antec external
hard
drive.

Thank you all for your time and help. It was very much appreciated, and
it
kept me plugging at it until I was able to nail the guilty party and get
it
resolved. :-)

The guilty party is actually Microsoft, no surprise. I had a similar
experience. It seems that external drives especially if they are setup
as external ESATA can confuse Vista, even XP, probably because your
system didn't have a up today controller designed specifically for
Vista. So Vista being really, really stupid ends up trying to boot off
a non system disk, likely your external or just flat out refuses to
see the external unless and until your fool around with the order your
external drives are plugged into your MB or it might generate a Blue
Screen of Death, not booting at all.

Of course the moronic fanboy crowd with try to point their finger
exclusively at third party hardware makers. They always do. But
wait... AHCI specs were originally written way back in 2004! Long
before Vista was ever released.

Following is NOT an attempt to explain YOUR specific problem, rather
to expose Microsoft's way of doing business.

http://www.intel.com/technology/serialATA/index.htm

Learn more here:

http://en.wikipedia.org/wiki/Serial_ATA

Finally the wooden stake through the heart

http://www.answers.com/topic/advanced-host-controller-interface?cat=technology

Common problems switching to AHCI under Windows:

Enabling AHCI in a system BIOS will cause a 0x7B Blue Screen of Death
STOP error on installations of Windows XP where AHCI/RAID drivers for
that system's chipset are not installed. Switching to AHCI mode
requires installing new drivers before changing the BIOS settings.

When attempting to install Microsoft Windows XP or a previous version
on an AHCI-enabled system will cause the setup to fail with the error
message "set up could not detect hard disk drive...". This problem can
only be corrected by either using a floppy disk with the appropriate
drivers, by slipstreaming the appropriate drivers into the Windows XP
installation CD or by turning on IDE emulation in the BIOS settings if
available.

Enabling AHCI in a system BIOS with Windows Vista already installed
will result in a BSoD if SATA has been running in IDE mode during
Vista's installation. Before enabling AHCI in the BIOS, users must
first follow the instructions found at Microsoft Knowledge Base
article 922976.

Enabling AHCI in a system BIOS on installations of Windows XP or
Windows Vista, will cause SATA Optical drives to disappear. A Hotfix
for Windows Vista is available under the title: "SATA optical drives
are not available after you start a Windows Vista-based computer."[3]

Now why do I bring this all up? Simple. The Vista DVD COULD have and
should have come with a generic AHCI controller or minus that some
warning about ESATA drives and the problems you will likely run into.
But the idiots of Redmond said screw that... just like they said screw
making sure popular printers and scanners under Vista will support ALL
the features they did under XP.

Need proof? Check Adam Albright's revealing post documenting
confidential emails between various Microsoft big shots including
Ballmer that not only acknowledged these shortcoming, but try to hide
them... until it came out during Discovery during a court case.
Another reason Microsoft is often referred to as the Evil Empire.
They don't give a crap how much harm and grief they cause users by
taking shortcuts. In fact they go out of they way to get you to
upgrade to Vista allowing some MB makers to use a Vista Certified logo
when they got to know damn well the product was shipped without some
necessary drivers.

Of course the fanboy crowd rather bow down and blindly worship
Microsoft, no matter what facts get in the way that almost always
points to them being a big part of the problem.
 
For some reason, the BIOS is still wanting to put that drive first. I have
changed it in the BIOS *2* times. I am not sure why this is happening. The
external drive was attached/installed long after the original install of
Vista since January this year. It has been working fine. Not sure why this
keeps changing in the BIOS, or why it was there to start with. There is
*no* operating system installed on that drive, it is a data backup only
drive. So I don't understand why it is being seen first when it is on. That
is at this point the puzzling part.

Jan :)
 
Colin Barnhorst said:
I agree that usb drives should not be connected during installation or
upgrade of Windows and I have had a couple of enclosures that prevented a
boot or caused Windows Explorer to stop working, but I have never seen
anything change boot order settings like this.

I have a USB optical drive attached. If it is powered up during boot up,
the machine will try to boot from it, rather than the internal optical
drive.
 
Have you changed the boot order in the BIOS to something like floppy,
optical, hard drive, followed by the others? As long as a bootable hard
drive is ahead of any usb selections you should not have this issue.
 
That's what I was afraid of (that the change you made was not persistent).
I can probably expect the same thing on my next restart. At least I know it
is not unique to my box, which would be a scary thought.

I'll bet something has happened in the last few days. I think we better
keep our ears to the ground. 'Tis a puzzlement.
 
Colin Barnhorst said:
I generally don't discuss the MSDN downloads in the general ng,

Neither do I, but then, you are the one who posed the specific question, not
me.
but yes I do now about those. However, I was thinking in terms of licenses
which permit
Thank you, however, as a long time subscriber to both I am very familiar
with the rules and regulations regarding use the the software, and do
comply. However, for the record, I do own several legal copies of the
software that I use on my personal and production machines.

Jan :)
 
Colin Barnhorst said:
That's what I was afraid of (that the change you made was not persistent).
I can probably expect the same thing on my next restart. At least I know
it is not unique to my box, which would be a scary thought.

Indeed! I have not had this happen before, so that is why it took me so long
to put the two together. However, I have not used an external drive before
so didn't know what to expect when I had to do a reinstall. But, now I know
to check the BIOS if it should happen again.
I'll bet something has happened in the last few days. I think we better
keep our ears to the ground. 'Tis a puzzlement.

It sure is a puzzlement! And one that bears watching. I have kept the
notes I posted here so that I have a record when the time comes to reinstall
again. I think that I will pass the information on to the mfg. so that they
are aware of the changes that are taking place in the BIOS and they may want
to do so checking on their end. It is definitely related to the external
enclosure in some way, as it just started since I installed the enclosure.
When the BIOS moves the external drive ahead of the bootable drives I get
the problem. The thing is when the machines has to do the required reboots
for updates and such this issue could come up again, and again if the
external drive is on at the time. I really need to find out what is
triggering the BIOS to make the change in the first place, as something is
causing it to change.

Jan :)
 
Here is a bit more information from a colleague that might help others:

"If all is right you could also in the BIOS disable the option to boot other
devices and only the internal would have been available to boot from. Some
Bioses even have the option to set the USB drives to be selectable at boot
to use if needed to boot from.

I think those problems you have discovered are all connected due to the MB
is also capable to be used and is designed with a server in mind."

Not sure this would apply to the problems you and others are having, but,
thought I'd try the suggestion about disabling the option to boot other
devices and see it that will keep the proper device lineup in the BIOS here.

Jan :)
 
Good information, but what triggered the reordering in the BIOS
spontaneously? You associate it with a usb effect but that can be a
coincidence. The one common thread that may well be involved is updating.
You were installing (and no doubt updating) and I had an security update on
6/27. Just for grins see if you have KB940157 in your history. My last
restart was after installing Windows Search 4.0 which I decided to try out
two days ago. Do you use that?
 
Colin Barnhorst said:
Good information, but what triggered the reordering in the BIOS
spontaneously? You associate it with a usb effect but that can be a
coincidence. The one common thread that may well be involved is updating.
You were installing (and no doubt updating) and I had an security update
on 6/27. Just for grins see if you have KB940157 in your history. My
last restart was after installing Windows Search 4.0 which I decided to
try out two days ago. Do you use that?

No...that KB update is not in my History list. I have not finished
installing all the Updates, as they keep popping up, as it rather normal
with installing a new OS and software programs. My system is a 64 bit, and
the version of Ultimate I am using is x64. Are you using the same?

Jan :)
 
Yes, Vista Ultimate x64, no multi-booting.

Jan :) said:
No...that KB update is not in my History list. I have not finished
installing all the Updates, as they keep popping up, as it rather normal
with installing a new OS and software programs. My system is a 64 bit, and
the version of Ultimate I am using is x64. Are you using the same?

Jan :)
 
Back
Top