From: do-not@respond.please   
      
   On Mon, 02 May 2011 21:35:05 -0700, Wes Groleau   
    wrote:   
      
   > On 05-01-2011 16:21, Java Jive wrote:   
   >> [skipping ahead]   
   >> insists that it has no knowledge of any other type of disk controller   
   >> other than that in the hardware it was originally installed, so if you   
   >> move the system disk to another machine which needs a different boot   
   >> driver to read the disks, you'll likely get a 'Blue Screen Of Death'   
   >> (BSOD) error such as 0x0000007B "Inaccessible Boot Device".   
   >   
   > I expected that when trying to boot from the swapped hard drive,   
   > to be fixed by booting from an install CD and doing a repair   
   > instead of an install.  But (trying to) use the hard drive   
   > gets a character-type display with only an underscore in the   
   > upper-left.  CD gets most of the way through booting, i.e.,   
   > loading all sorts of drivers, most clearly not being needed   
   > for the hardware, and then says something is seriously wrong,   
   > 0x0000007B   
   >   
   >> If it's the same as Windows 2000, immediately after the CD boots into   
   >> the blue installation screen, there is message across the top saying   
   >   
   > Doesn't get that far.  I checked the CD on my Mac, and apparently   
   > it's not my MSDN CD.  It looks like a normal install CD, except that   
   > the volume name is HPSETUP.  I never had an HP, so I'm not sure where   
   > it came from.  But that explains why it didn't work.   
      
      
   Of course you have an HP!   
   You started this discussion stating that the HP laptop broke its hinges!   
   :-)   
      
      
      
      
      
      
   >   
   >> something like: "Press F6 to install extra installation drivers"   
   >> (don't blink or you'll miss it).  If then you press F6, what is   
   >> expected is that you have a floppy with suitable boot drivers and a   
   >> text file called TXTSETUP.OEM, similar in layout to, but unfortunately   
   >> not exactly the same as, an INF file.  (W7, and therefore probably   
   >> VISTA, will accept the standard INF file, which is much more   
   >> convenient, but the mechanism to get it to read the floppy is a lot   
   >> less so).   
   >   
   > Considering it has no floppy, a very lot less convenient.   
   >   
   >> Therefore, unless you can find one for the new laptop's motheboard or   
   >> chipset, you're probably going to have to write your own TXTSETUP.OEM   
   >   
   > Thanks, but I do far too much of that kind of hacking at work.   
   > I'm not going to do it at home to bail out a twenty-year-old whom   
   > I advised another approach.  Plus, I also pointed out to him   
   > that he can get Windows Seven _legally_ for twenty bucks   
   > through the college's special contract with Microsoft.   
   >   
   > Twenty bucks too much to pay to fix a three hundred dollar   
   > mistake?  Apparently--he dug out his Office disks and   
   > is installing it on the new box.  Plans to do the same   
   > for his Comp. Sci. IDE.   
   >   
   > Thanks for trying to help us out.  Too bad he prefers   
   > using money over using patience.  :-)   
   >   
      
      
   --   
   Using Opera's revolutionary email client: http://www.opera.com/mail/   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)