| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 86183 | 2008-01-07 07:22:00 | Can't install NT-Based OS, hangs but doesn't freeze | Agent_24 (57) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 628175 | 2008-01-07 20:43:00 | The BIOS is stuffed. | pctek (84) | ||
| 628176 | 2008-01-07 20:46:00 | Written badly by chaintech idiots or bad chip? | Agent_24 (57) | ||
| 628177 | 2008-01-07 20:59:00 | I dont think the chip is stuffed . Since it detected the hdd's in post 10 . And 98 and Ubuntu wouldnt install at all . If the BIOS was knackered . Coz it wouldnt find anything (ie: the hdd's), if it was stuffed . There maybe a later BIOS update somewhere . And it looks like there maybe a later version - 26/10/99 BIOS, around somewhere . Hmm is this a Socket 370 mobo?? Have you been here ? ( . chaintech . com . tw/eng/a2111_product_download . php?serno=237" target="_blank">www . chaintech . com . tw) |
Speedy Gonzales (78) | ||
| 628178 | 2008-01-07 21:23:00 | The rar file on the above site In 6asa\6asa\1999, under the 6ASA0C07.TXT file it says: Date: 12/07/99 Feature: for win2000 install fail . (Which could be why its not installing on NT systems). This is the BIOS version you've got. 6ASA0C07.bin is dated 7/12/99. Which MAY fix your prob. |
Speedy Gonzales (78) | ||
| 628179 | 2008-01-08 06:33:00 | I dont think the chip is stuffed . Since it detected the hdd's in post 10 . And 98 and Ubuntu wouldnt install at all . If the BIOS was knackered . Coz it wouldnt find anything (ie: the hdd's), if it was stuffed . There maybe a later BIOS update somewhere . And it looks like there maybe a later version - 26/10/99 BIOS, around somewhere . Hmm is this a Socket 370 mobo?? Have you been here ? ( . chaintech . com . tw/eng/a2111_product_download . php?serno=237" target="_blank">www . chaintech . com . tw) It's slot 1 but would take socket370 on a slocket no doubt . . . that is the BIOS I used - remember I think these dates are in american format, which is confusing . The rar file on the above site In 6asa\6asa\1999, under the 6ASA0C07 . TXT file it says: Date: 12/07/99 Feature: for win2000 install fail . (Which could be why its not installing on NT systems) . This is the BIOS version you've got . 6ASA0C07 . bin is dated 7/12/99 . Which MAY fix your prob . 6ASA0C07 is the one I'm using currently, unless they're not using american date formatting, but I'm pretty sure I'm using the latest one (I downloaded that RAR file before too) Not sure why they call it Socket 370 |
Agent_24 (57) | ||
| 628180 | 2008-01-08 06:44:00 | It'd be pretty stupid, if this (Feature: for win2000 install fail) is a feature of the latest BIOS then If you've got the latest version. Not much you can do about it. You'll have to email whoever, and get them to fix it. That'll be the reason why you cant install NT Os's on that system. |
Speedy Gonzales (78) | ||
| 628181 | 2008-01-08 07:27:00 | It'd be pretty stupid, if this (Feature: for win2000 install fail) is a feature of the latest BIOS then If you've got the latest version . Not much you can do about it . You'll have to email whoever, and get them to fix it . That'll be the reason why you cant install NT Os's on that system . HAHAHAHAHA :lol: Yeah you can install Win2000 fine on all the other BIOS versions, except that one, which is designed to make it fail! I guess I could try the BIOS revision before that one, just for a joke . . . . Wouldn't get my hopes up trying to convince chaintech to do any work on that BIOS |
Agent_24 (57) | ||
| 628182 | 2008-01-08 08:54:00 | Well somebody's going to laugh at this one.... So I bumped the BIOS version down one, to 6ASA0504.BIN - and would you believe it - windows setup actually started!! Now before you think that Chaintech are genuinely insane and their last BIOS update was to write a BIOS that caused all NT based OS to fail installation, I have to point out that this apparent fix didn't work. While windows setup loads all the files, just as it tries to start windows, it bails with a nice BSOD about ACPI Compliancy, or rather, my BIOS's lack of it: www.imagef1.net.nz So either Chaintech decided that Windows NT doesn't work, therefore they should make their last BIOS cause windows NT setups to hang, and thus try to hide the fact that they can't write the ACPI portion of their BIOSs for peanuts, or they genuinely fixed it and something else is wrong here. I'm going to try again removing all unnecessary components from the PC, and just see what happens... Otherwise apparently I can install windows fine if I don't use ACPI, which might be OK, although I'd rather have it fixed. |
Agent_24 (57) | ||
| 628183 | 2008-01-08 10:00:00 | I have to ask....why are you even bothering with a P2-350??? :confused: Just put win98 or linux on it. XP is never going to run too well on it anyway.:D |
CYaBro (73) | ||
| 628184 | 2008-01-08 18:17:00 | While windows setup loads all the files, just as it tries to start windows, it bails with a nice BSOD about ACPI Compliancy, or rather, my BIOS's lack of it: . imagef1 . net . nz/files/acpi_fail_bsod . jpg" target="_blank">www . imagef1 . net . nz Try this for XP ( . microsoft . com/kb/314830" target="_blank">support . microsoft . com) Or this for 2000 ( . microsoft . com/kb/256841" target="_blank">support . microsoft . com) Yup it sounds like thats what the prob is . You wont fix it, but it may still work, if you install the standard PC HAL, not the ACPI HAL . |
Speedy Gonzales (78) | ||
| 1 2 3 | |||||