![]()
[<<]Message[>>] [<<]Author[>>] [<<]Subject[>>] [<<]Thread[>>]
Number : 1864 Date : 2002-03-28 Author : Kan Yabumoto Subject : Re: "No Operating System" error message Size(KB) : 2
I have some experience with EZ-BIOS. Apparently, it needs to make a patch to some hidden sector somewhere of the C: drive to fool the system that the disk dimension (cylinder, head, sector and track count) that is originally detected by the old BIOS (which cannot handle the large hard disk --- probably beyond the 32GB barrier which older BIOSes cannot handle) and initialize with some new fudged disk parameters before the BootSector takes control. My suggestion under the circumstance is to use the MaxBlast+ (the diskette you were using when you were initializing EZ-BIOS) and install EZ-BIOS on the drive which will become new C: drive. It is my understanding that EZ-BIOS needs to be at the C: drive when you boot up whether the large-size drive is actually setup to C: or not. So, my guess is that in your original configuration, the EZ-BIOS patch was done on your old C: drive and accessed your D: (or whatever new drive as the destination). When you switched your new drive to become C:, it did not have the EZ-BIOS patch in the drive. So, go back and install EZ-BIOS on the drive on whatever becomes the new C: drive. Anyway, your problem was related to EZ-BIOS and the way the system was accessing your hard disk, not XXCOPY's fault. The best way to deal with this situation ultimately, is to upgrade your BIOS. When you install the NT/2K/XP version, you will not get around this problem because the NT-series of Windows bypasses the BIOS (and EZ-BIOS-modified) disk parameter values and any discrepancies it find will result in a fatal error. Kan Yabumoto ================================================================ At 2002-03-28 11:30, you wrote: >Kan, >Thanks for the quick response! You're correct in the assumption it is >W98, however, I did run the full format and surface verify before >starting the process (and made the boot diskette you suggested which >is much quicker as promised). I had tried to copy the files to the >disk previously on an earlier attempt and assumed that the format and >XXCOPy operations would completely wipe the HD and give me a clean, >working copy in the end. Maybe that's part of my problem. As this is >an older computer, the current HD uses Maxtor's EZ-BIOS when it >boots. >Not sure if that's playing into it also but never got that far into >the boot to find out. I'll try your suggestions tonight when I get >home (have to earn the bucks to pay for all this high tech stuff for >the kids, you know!) and let you know how it turns out. Again, >thanks >a lot for the help in advance!! >Lee > >-
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.