Unsolved
This post is more than 5 years old
7 Posts
0
11249
May 31st, 2002 16:00
Win NT4 on a Dimension 8200 - scratch installation
Hi!
I have tried to install NT4 on the company's new Dimension 8200 (Intel 850E chipset). I have partitioned the hdd with PQ Magic: Moved forward and hid the primary XP (NTFS) partition. Created a new FAT16 (primary set to active) and a secondary (M$ calls it extended) with two logical NTFS-partitions in it. So far so good. After booting with the W98-bootdisk with CD-rom driver support (with added smartdrv.exe) I finally started winnt.exe.
At first it crashed pretty late in the winnt.exe- install program (which I related to the lack of ATA100-controller driver). After I've copied the i386-directory to C: (my FAT16) I replaced original NT-files with the ones in SP4 (which are the only SP I have on CD).
NT now crashes in NT's own boot-program ntldr and so on... which is supposed to continue with NT-setup in graphical mode. Early startup goes fine, but when the classic blue startup-screen (showing info about CPU, memory and Built-no.) should switch to graphic mode it crashes.
After some complements to boot.ini (switch /CRASHDEBUG) I see a blinking text, "SND", to the right in the "crash-info-blue-screen" :-). "irql: 1e" is possibly the troublemaker but it actually doesn't tell me a thing.
I think I need a chipset driver for this motherboard. I think that's the main problem.
To my questions:
Q1: Is it possible to install NT 4 on Dimension 8200 (850E chipset, ATA100 controller)? The salesman actually told me so...
Q2: If not driver-problem, what could it be?
Q3: "When" do I add the driver: a) Same time as the SCSI-driver?
b) Unpack SP6a and copy files to i386-directory prior to install? If yes- How do I unpack SP6a?
c) Something else...
OK! Now you have something to chew on (swedish expr.)
I have tried to install NT4 on the company's new Dimension 8200 (Intel 850E chipset). I have partitioned the hdd with PQ Magic: Moved forward and hid the primary XP (NTFS) partition. Created a new FAT16 (primary set to active) and a secondary (M$ calls it extended) with two logical NTFS-partitions in it. So far so good. After booting with the W98-bootdisk with CD-rom driver support (with added smartdrv.exe) I finally started winnt.exe.
At first it crashed pretty late in the winnt.exe- install program (which I related to the lack of ATA100-controller driver). After I've copied the i386-directory to C: (my FAT16) I replaced original NT-files with the ones in SP4 (which are the only SP I have on CD).
NT now crashes in NT's own boot-program ntldr and so on... which is supposed to continue with NT-setup in graphical mode. Early startup goes fine, but when the classic blue startup-screen (showing info about CPU, memory and Built-no.) should switch to graphic mode it crashes.
After some complements to boot.ini (switch /CRASHDEBUG) I see a blinking text, "SND", to the right in the "crash-info-blue-screen" :-). "irql: 1e" is possibly the troublemaker but it actually doesn't tell me a thing.
I think I need a chipset driver for this motherboard. I think that's the main problem.
To my questions:
Q1: Is it possible to install NT 4 on Dimension 8200 (850E chipset, ATA100 controller)? The salesman actually told me so...
Q2: If not driver-problem, what could it be?
Q3: "When" do I add the driver: a) Same time as the SCSI-driver?
b) Unpack SP6a and copy files to i386-directory prior to install? If yes- How do I unpack SP6a?
c) Something else...
OK! Now you have something to chew on (swedish expr.)
No Events found!
fireberd
11 Legend
•
33.4K Posts
•
112.8K Points
0
May 31st, 2002 22:00
**There is no Guitarist like a Pedal Steel Guitarist**
Kanuk001
472 Posts
0
May 31st, 2002 23:00
SP3 or SP4 corrected this issue. You might want to post the information from the blue screen along with the configuration of your 8200.
Why run NT? Are you setting up a museum of old OS's?
Charles,
Tag # 6VMY111
Dimension 8200, Bios A05
1.8 ghz P4
512 mb Rambus Ram
80 gb HD primary, 20 gb HD secondary
NVidia GEForce3 TI200
Dell M991 monitor
Samsung 308b DVD/CDRW combo
Telephony modem
Turtle Beach Santa Cruz Sound (4161 beta driver)
Altec Lansing ADA995 (1BT)
Windows XP Home
(Multibooted with Win98, Win2000, OS/2, Linux)
Roxio Easy CDCreator 5.1.0.104 (platinum)
Office XP Pro (retail)
Power DVD 4 (retail upgrade)
Norton SystemWorks 2002 (retail)
gullan
7 Posts
0
June 3rd, 2002 12:00
HeHe, well not a museum... Since this machine will stand as a workstation in a NT 4 -network and we have a very good relation to NT 4 (SP6a and all), we actually don't see any reason at all to upgrade. Neither the workstation nor our whole network ($ you know). Additionally, we have some NT4 licenses we want to use. Of course M$ and probably Dell and Intel to (which I suppose get reducted price if they "force" people to upgrade) all "want" me to BUY new OS-license...
I have spoken to 2nd line support in Sweden. They gave me the advise to switch the graphicscard (an 'nVidia 64MB DDR GeForce3 Ti200) with an older one (I happen to have a nice Diamond Viper V550 in my closet ;-) and install SP6a and localize the appropriate NT4-driver for the new card. And install the new... So shall be it. I will come back to tell ya all how things go :-)
If you have any more ideas, please don't hesitate to write i line :-)
Thanks
/gullan from Sweden
gullan
7 Posts
0
June 20th, 2002 14:00
A combination of things made the installation possible.
After triing to install the AGP-card Viper 550, I realized that the AGP 2x/4x standard is totally different from AGP 1x !? I didn't know that :-). Lucky me I had an even older PCI-card; ATI Mach32 :-). After installing this and switched primary graphics controller setting in CMOS to PCI I tried again with installation. Same crasch at the same "place" :-(.
I didn't give up. I now realized that the problem was elsewhere.
I saw two possible reasons:
1) Problems with IRQ-management in BIOS contra (vs) NT's handle of BIOS configuration.
2) NT's old drivers (which probably results in problem 1) )
I tried to do some IRQ-settings in CMOS but I'm not sure if this is/was necessary. I manipulated IRQ's for a while which led to same crasch...
I figured the newest service pack (SP6a) might solve the problem, or at least take me longer in install-process.
But how do I upgrade a non-existent NT-system?
This was my solution:
*) Open SP6a full exe-file with Winzip (not execute the file).
*) Unzip all files to a folder.
I noticed all files now was unpacked. The files in the NT i386 -install folder actually were packed ( the filenames ended with an underscore, f.e. win32k.sy_ instead of win32k.sys ). I hoped that the installation program rather would take an unpacked file before a packed dito.
*) I copied all SP6-files to the i386-install folder.
Mistake. A new installation resulted in the same crasch.
*) I used my old Norton Commander to localize all files that were packed and unpacked and removed all packed files from i386-folder.
*) And guess what? Installation completed without a crasch. :-)
Thank you all and good bye for now!
/Gullan