VOGONS


NT 4.0 Installation woes

Topic actions

Reply 20 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
fosterwj03 wrote on 2025-04-13, 19:37:

Yes, the i386 folder is all you need.

In that case ...

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 21 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie

Made it to 16% 🙁

Tried installing on spinning rust - BSOD

Trying NT3.51 now ...

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 22 of 62, by fosterwj03

User metadata
Rank Oldbie
Rank
Oldbie

That is just weird. It boots into the NT kernel far enough to start transferring files, but then crashes. I'd suspect a drive error, but you said it happens with a different hard drive.

I wonder if updated NT files would help. You could try to slipstream Service Pack 6 using Bearwindows' instructions.

https://bearwindows.zcm.com.au/winnt4.htm

You wouldn't need to make a new CD. You could transfer the updated i386 folder directly to your destination drive and run the DOS setup again.

Reply 23 of 62, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

Is the ram healthy?

The error in question happens when memory owned by a driver fails to be either read or written to, at the correct IRQ Level. If it is being serviced by an emergency handler, that would do it-- such as from a general failure.

Try running memtest on this system.

Reply 24 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
wierd_w wrote on 2025-04-16, 04:17:

Is the ram healthy?

The error in question happens when memory owned by a driver fails to be either read or written to, at the correct IRQ Level. If it is being serviced by an emergency handler, that would do it-- such as from a general failure.

Try running memtest on this system.

I did run memtest86+ on it, as I was thinking the exact same thing, albeit only for 12 hours. I could off course just try slipping in some other RAM ...

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 25 of 62, by myne

User metadata
Rank Oldbie
Rank
Oldbie

What servicepack is the iso?
Best to use a slipstreamed sp6 if you can

Can't hurt to disable anything not strictly necessary in the bios.
Eg parallel, serial.
Also play with other settings like vga IRQ on/off,ide modes on/off.

I had a board that didn't work with block mode or whatever it was enabled.

I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11+tcp+vbe_svga auto-install iso template
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic

Reply 26 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
myne wrote on 2025-04-16, 05:42:
What servicepack is the iso? Best to use a slipstreamed sp6 if you can […]
Show full quote

What servicepack is the iso?
Best to use a slipstreamed sp6 if you can

Can't hurt to disable anything not strictly necessary in the bios.
Eg parallel, serial.
Also play with other settings like vga IRQ on/off,ide modes on/off.

I had a board that didn't work with block mode or whatever it was enabled.

It's an SP1 ISO - I was actually considering finding one without SP 🤣

Yeah, maybe some BIOS tweaking would be an idea.

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 27 of 62, by myne

User metadata
Rank Oldbie
Rank
Oldbie

Forwards in sp is the way to go.
Just find sp6 iso and see if it resolves.
There were many years of bugfixes.

Presumably it's OK to link to standard Windows isos...
https://archive.org/details/WinNT40SP6aISOEXE

I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11+tcp+vbe_svga auto-install iso template
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic

Reply 28 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
myne wrote on 2025-04-16, 06:16:
Forwards in sp is the way to go. Just find sp6 iso and see if it resolves. There were many years of bugfixes. […]
Show full quote

Forwards in sp is the way to go.
Just find sp6 iso and see if it resolves.
There were many years of bugfixes.

Presumably it's OK to link to standard Windows isos...
https://archive.org/details/WinNT40SP6aISOEXE

Thanks!

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 29 of 62, by myne

User metadata
Rank Oldbie
Rank
Oldbie

Success?

I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11+tcp+vbe_svga auto-install iso template
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic

Reply 30 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
myne wrote on 2025-04-17, 03:02:

Success?

Haven't been home to try yet, will get to it tomorrow or Saturday

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 31 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie

But that ISO doesn't look like it can install NT with SP6? (doesn't have winnt.exe in the i386 folder)

Would I add the contents of the i386 folder to the original i386 folder?

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 33 of 62, by myne

User metadata
Rank Oldbie
Rank
Oldbie

I just linked the first one I saw. there are plenty more.
https://archive.org/search?query=nt4+sp6+iso

I built:
Convert old ASUS ASC boardviews to KICAD PCB!
Re: A comprehensive guide to install and play MechWarrior 2 on new versions on Windows.
Dos+Windows 3.11+tcp+vbe_svga auto-install iso template
Script to backup Win9x\ME drivers from a working install
Re: The thing no one asked for: KICAD 440bx reference schematic

Reply 34 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie

Ok, thanks, I'll be looking into it 😀

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 35 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie

Now what ...

I thought I could succesfully install DOS 6.22 on that CF card, BUT... I don't think I ever did more than install it, didn't boot or anything ...

Now, after installing DOS 6.22 it just shows "Error!" after startup?

I've tried both settings for IDE drive - same story.

On a 128 MiB CF card, it starts fine, but that's kinda too small to install NT, right?

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 36 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie

On the other hand ... I messaged a friend saying that I installed 6.22 on that CF card, and that the "HIMEM is testing extended memory" took forever with 64 Megs ... So apparently that HAS worked.

I deleted all partitions with FDISK and let MS-DOS 6.22 make its own partinion. But no, "Error!" ...

'bout to give up on that shizzle

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 37 of 62, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

How large is the cf card you are using?

Larger than 8gb?

Edit: 512mb

Is your system impacted by 504mb int13 limit?

Reply 38 of 62, by H3nrik V!

User metadata
Rank Oldbie
Rank
Oldbie
wierd_w wrote on 2025-04-18, 21:17:
How large is the cf card you are using? […]
Show full quote

How large is the cf card you are using?

Larger than 8gb?

Edit: 512mb

Is your system impacted by 504mb int13 limit?

I'm not sure about the int13 limit. It came with a 1.2GB drive when I got it, so I assume that it's not an issue. It's a PCI motherboard with BIOS from 1996, I would think that would be changed by then? Or is it an option I need to set somewhere in BIOS?

If it's dual it's kind of cool ... 😎

--- GA586DX --- P2B-DS --- BP6 ---

Please use the "quote" option if asking questions to what I write - it will really up the chances of me noticing 😀

Reply 39 of 62, by wierd_w

User metadata
Rank Oldbie
Rank
Oldbie

The bios screen says it understands LBA, so it really should NOT be impacted by the 504mb limit imposed by the OG version of INT13. (which plagues 386s and early 486s) However, it might be affected by the 8gb "large CHS" limit.

Anyhow, that would not affect a 512mb drive.

I am not sure why your late era 486 is having these issues.

Clarification:

The early CHS addressing method ran into a brick wall when used with DOS. While INT13 could address drives larger, using more heads and more sectors per track, DOS has a restriction that reduces these values by 1, and it results in a maximum permitted drive geometry of 504mb. This is a limit usually found on XTs, 286s, and 386s, but some very early 486 boards are affected.

Your board's drive geometry screen says it knows how to talk LBA though, so it should not be impacted.

the 8gb limit is a similar situation, but with the "Large CHS" addressing method. With that, DOS cannot see drives larger than 8gb without help, such as from an option rom, or from a DDO.

Again though, your BIOS says it does LBA, and that should not be an issue. Your drive is also smaller than 8gb, so again, would not be an issue.

WHY IT MATTERS:

NT4 has to START with the DOS int13 interface, until it can load NTLDR , the HAL, and then the 32bit disk controller drivers (to enter LBA24 mode). This means the boot drive has to obey the limits of the INT13 implementation present. NT4 CAN use a DDO to get around this, since it only needs to be active during the first few seconds of the boot process, but it is not considered desirable.