Results 1 to 15 of 15
  1. #1
    Joined
    Nov 2000
    Posts
    25

    Angry

    i've posted this in the past, and never gotten an answer.....not a good one anyway.

    I dual boot ME and 2k on my a7v.
    after installing 2k and then SP1, i reboot, select win2k on the boot menu... it starts to load, then BAM, inaccessable boot device. What the hell?

    just so u dont ask. Both are on different partitions on the same drive, on my ata 66 controller.

    i'm going to try this again... for the billionth time.. except, i'll add SP2b. My bet is the same thing happens again.

    Any ideas are welcomed and appreciated.

  2. #2
    Joined
    Feb 2001
    Posts
    425
    Huh..well the ATA/66 controller on the A7V are the regular IDE controllers, not the Promise Ultra 100 controller..which is wierd..check out the boot.ini file in the root of your c:\ drive and make sure it is pointing to the right parition for Windows 2000.

  3. #3
    Joined
    Apr 2001
    Posts
    40

    Lightbulb Inaccessible boot device

    Sounds like a stupid advice but go to manufacturer's site and look for the jumper info for your SPECIFIC model number. I have a 40 gig Maxtor drive that does the same thing and guess what, the jumper instructions that comes with it is different than the one I got from their site. I followed the one from their site and I got my problem solved.

    [Edited by atedee on 04-27-2001 at 04:12 PM]

  4. #4
    Joined
    Nov 2000
    Posts
    25

    Re: Inaccessible boot device

    Originally posted by atedee
    Sounds like a stupid advice but go to manufacturer's site and look for the jumper info for your SPECIFIC model number. I have a 40 gig Maxtor drive that does the same thing and guess what, the jumper instructions that comes with it is different than the one I got from their site. I followed the one from their site and I got my problem solved.

    [Edited by atedee on 04-27-2001 at 04:12 PM]
    i've been using this HDD for well over a year.... always set on master. I dont see how i could have the wrong jumper settings. Can u explain what your problem was?


  5. #5
    Joined
    Jan 2001
    Posts
    11,859
    Were you overclocking when you installed the update? If so, you may have trashed some system files during the install.

    You can try running the emergency repair disk, then reinstall the update.. no overclocking.

    If you downloaded the update, you may have a corrupt file. Redownload it before reinstalling.

  6. #6
    Joined
    Nov 2000
    Posts
    25
    i'd tried it, overclocked, not overclocked...everything...several times....... but, i'm going to shut up now, cause i just noticed there WAS a jumper problem.. hmmph..... thank u.

    Now to install win2k and see if it works. Btw.. should i even bother with sp1? or just go straight to beta2?


  7. #7
    Joined
    Mar 2001
    Location
    34 South
    Posts
    422

    Question

    Hi

    Tell me the following
    -Did it dualboot before you installed the service pack?
    -Is the 2000 partition NTFS formated or not?

  8. #8
    Joined
    Nov 2000
    Posts
    25
    it was the jumper. problem solved.

    and yes... it always sucessfully booted before sp1.


    Something new though... win2k hangs on startup...
    ugh.

  9. #9
    Joined
    Nov 2000
    Posts
    25
    i've just installed win2k 6 times!

    i've tried everything, and i can't get 2k to boot normally....as in without a 5 minute wait.
    it just sits there as the progress bar gets half way.
    Almost like it's searching for something..... but there's nothing installed to search for!


  10. #10
    Joined
    May 2000
    Location
    ?
    Posts
    1,848
    I'm sure that I missed it but, did you list your hardware specs?

    Have you tried to install Win2K with the bare minimum?That is, just the essential components?

    Does Win2K operate normally when its the only OS installed?

    You installed WinME first, right?


  11. #11
    Joined
    Nov 2000
    Posts
    25
    a7v 1.02
    bios 1008b, also tried 1005b, and 1002 for a7v133

    700mhz, not overclocked at the moment.
    128 pc133

    350 watt ps
    lots of fans.
    many drives.
    The only things hooked up right now are NIC, dvdrom, and the ata66 hdd that i'm installing to.

    In the past, while dual booting, everything worked fine.
    This startup delay was never an issue.

    i've just finished my 8th install of the day. ntfs, fat, fat32.... i dont think there's anything left for me to try.

    Except... using a different cdrom to install. I just dont understand how that could affect this delay i'm getting at startup of win2k. Even in the install it does it.
    "Now starting windows 2000..." 5 minutes later... it finishes.

  12. #12
    Joined
    Nov 2000
    Posts
    25
    sorry for the language....but... •••• me sideways.

    I used a different cdrom to install, and it didnt hang anymore at start up.... all that after 9 installs of hell!

    ARRRGGGHHH

  13. #13
    Joined
    Nov 2000
    Posts
    25
    lol, it gets better.

    turns out..win2k just doesnt like that drive for some reason. I hooked it up again, and the problem returned.

    Excuse me while i go get the 10lb sledge.....

  14. #14
    Joined
    Jan 2001
    Posts
    11,859
    Ok.. so your saying you can install using one type of CDrom in the same IDE configuration, but not the other?

    Sounds more like the IDE may not be configured properly for the drive... perhaps you have DMA transfers active / or deactive?

  15. #15
    Joined
    May 2001
    Location
    N.S. Canada
    Posts
    4,137
    perhaps?

    i run win2k on ide , and after service pack one installed ...for some unknow dang reason, windows
    detected my "mass storage controller" as plug and play and installed the drivers(raid) for it, when i rebooted my windows would hang half way on the progress bar just as you described.
    I had to go into trouble shooting setup (F8) and select last known good configuration, run it, then it would alow me into windows.
    I disabled that raid contollers then everything went ok, reinstalled SP1 and its been ok, it was some bug glitch on the hang up having to do with the raid mass storage controller.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •