Announcement

Collapse
No announcement yet.

Can't install any OS at all... :(

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Can't install any OS at all... :(

    So, I got myself a new "little" PC for net stuff. It's a barebones ASUS thing with all the requisite bits, lovely. Problem is, it won't let me install any operating system to it.

    I can get it as far as a dos prompt with a Windows 98 boot disk, but any Microsoft OS gets only as far as "performing a system check" and then hangs with a black screen. This happens with 98 from the boot disk, ME and XP from the CD. As you might guess, Linux is (perhaps) a little more useful - it tries its best and then says, "Bad EIP Value" and "Interrupt Handler not Synching" before hanging.

    The system was bought with a blank HDD, but at times like this you realise that you haven't got a bloody clue about BIOSes and what have you. I genuinely thought that installing an OS to a blank HDD was as simple as slinging in the CD... clearly not. Is there anything in a BIOS that would cause this kind of problem? And if so, how can I fix it? And if not, does it mean that my hardware is broken somehow?

    I've tried disabling all the onboard devices, all the serial and parallel ports, all the USB controllers. None of it makes any difference at all.

    Anybody..? The mobo is an A7SC, which is billed as XP-compatible. It's got a 2600+ processor in it (according to the boot screen) and 512MB of DDR. I'd expect the processor and RAM to be compatible, given that I bought it as a package.

    Bastard machine

    #2
    Well... that's rather odd. I've always been able to just bung in a CD and have it work.

    Is the HDD formatted? It's not connected via a RAID or anything, is it? I'd be suprised if it was in a bare-bones system. If it is, you might need special drivers.
    To be honest, I'm not really sure.
    I hesitate to say it, but I'd be suspect of my hardware, personally.

    Comment


      #3
      This is a problem I've seen myself. The black screen is at the moment when Microsoft is updating the boot sector to point at the new installation.

      Go into your BIOS (its probably DEL on startup) and turn off virus protection. Frankly, leave it off; the days of bootblock viruses are long gone.

      Comment


        #4


        That sounded so right it couldn't be wrong... but given that I've spent last night finding bits of the bios that look like they should do the trick ("VGA is set to PCI rather than onboard! That must be it... awww, ****") I shouldn't have gotten my hopes up.

        No joy, I'm afraid, but cheers for the suggestions

        PC is currently down the street at my local repair place, where I've told them if they can get it as far as the blue Windows XP install screen I will love them forever. At least they can switch the RAM and HDD to see if they're the cause, I suppose.

        Comment


          #5
          See if you can download a low-level format util off the net. You will need to know the exact model/ make of your HDD (usually you do anyway), slap it on a floppy and kick it after you've got your 98 Boot Disc command prompt up.

          It'll take hours but it might just work.

          Comment


            #6
            It might be worth downloading the Knoppix Linux CD if you have broadband. It's obviously not going to help with a windows install, but it may get you into the system so that you can troubleshoot it in case anything is faulty. It can boot straight off the CD into a fully working Linux distro (2 gigs worth of software) and has great hardware detection.

            Comment


              #7
              Any updates on this Dai?

              It sounds HD related (perhaps cable/wrong way round?)
              I'd be interested to find out what the issue is/was.

              Comment


                #8
                Good work Yashiro, that's exactly what it was

                According to Guy In The Shop, "IDE cables weren't done right, and the jumpers were all ****ed up", or something. Hardware - the bane of my life

                In any case, it works now, and I'm on it as I type... now comes the joy of reinstalling XP and the blaster patches, etc, etc, etc, etc

                Cheers for all your assistances, much appreciated.

                Comment


                  #9
                  If you'd been on IRC I'd have got that sorted in a jiffy. (for free!)


                  Get yourself on there if you have any more issues.

                  Comment


                    #10
                    OK, I had this problem at the weekend with an ASUS A7V600. My friend from work and I built up my PC. Booted up all seemed fine. Went to install XP and it crashed out, blue screening half way throught the install etc etc. In the end we manually set the memory to 266mhz and it installed fine. You could probably bump it up a bit to 333 but I think the memory was not auto detecting or if it was it wasn't detecting the right speed. Also you will find tonnes of fiddles to do on the motherboard to optomize the who thing (Mainly graphics in my case.) Which is nice but complicated. You may want to make sure you have the right cpu speed selected as that was also wrong for me, I ended running it too slow until I realised it had no autodetect.

                    --edit--

                    Dam should have read down the bottom as well, oh they fixed it did they, hmmmm I wouldnt belive them personally. Sounds like they are plumbers coming to fiddle with stuff that isnt broken to me.

                    Comment


                      #11
                      Well, conspiracy theories aside mine wasn't even getting as far as the windows installer. It got to the "Checking Hardware" bit that XP does as soon as you put the CD in, then died, every time.

                      While I'm here, though, my processor was advertised as a 2400, BIOS calls it a 2600+ but it's clocked to 1600... if I set it to the other default in the BIOS (2133), windows doesn't start. What should I be looking at to get it up to full speed? There's a "manual" bit, but it involves multipliers and what have you... scary

                      Comment


                        #12
                        I don't know the speed of all the AMD processors, but a 2400+ doesn't mean it'll run a 2400mhz.

                        The way the multipliers and FSB(Front Side Bus) work is easy. You PC should be running at a FSB of 333 mhz or 400mhz depending on the ram. The speed the CPU runs at multiple of the FSB e.g. 400 x 5.5 will give you a processor speed of 2200mhz and so on.

                        Comment


                          #13
                          Not quite. The real FSB is half the quoted 'double pumped' FSB.

                          Top end 3200 Barton runs at 200Mhz (400Mhz)
                          Has an 11x multiplier.

                          200 x 11 = 2200Mhz

                          PR Rating 3.2Ghz
                          Real Clock speed 2.2Ghz

                          http://www.muisejt.com/axp.html has a table that seems to be accurate.

                          Comment


                            #14
                            Originally posted by yashiro
                            Not quite. The real FSB is half the quoted 'double pumped' FSB.

                            Top end 3200 Barton runs at 200Mhz (400Mhz)
                            Has an 11x multiplier.

                            200 x 11 = 2200Mhz

                            PR Rating 3.2Ghz
                            Real Clock speed 2.2Ghz

                            http://www.muisejt.com/axp.html has a table that seems to be accurate.
                            Woops, I knew something was wrong with my description.

                            Comment

                            Working...
                            X