It could be because NT 3.51 has never been distributed on a bootable CD, so maybe the loader and ntdetect don't support that. Which boot sector are you using, I presume an NT4 or newer one? Try to put the matching loader (either ntldr or setupldr) and ntdetect.com files in as well. I had the same issue when trying to make an ISO of Windows 2000 build 2124 bootable with either a build 2128 or 2195 boot sector, none worked, all gave that error message.
If I remember correctly, someone made a bootable iso of daytona back in the osba days, is that here on
any of the servers, perhaps you can check on how it was made bootable.
That wouldn't work because the boot floppies made in the NT 3.51 setup expect that all the files from the DOS portion of the setup to already be there. To make it bootable, you could add a DOS floppy and in the autoexec.bat run the setup after loading a few CD drivers.
That wouldn't work because the boot floppies made in the NT 3.51 setup expect that all the files from the DOS portion of the setup to already be there. To make it bootable, you could add a DOS floppy and in the autoexec.bat run the setup after loading a few CD drivers.
That won't work. The DOS part expects you to create three floppies, and A: will be an emulated read-only floppy. The only way I see something like this working is somehow using memdisk to emulate a hard drive, and writing an NT driver to read it while in protected mode (as memdisk only traps BIOS calls).
That wouldn't work because the boot floppies made in the NT 3.51 setup expect that all the files from the DOS portion of the setup to already be there. To make it bootable, you could add a DOS floppy and in the autoexec.bat run the setup after loading a few CD drivers.
That won't work. The DOS part expects you to create three floppies, and A: will be an emulated read-only floppy. The only way I see something like this working is somehow using memdisk to emulate a hard drive, and writing an NT driver to read it while in protected mode (as memdisk only traps BIOS calls).
It'll work if you use a DOS boot disk as the boot image file and then have autoexec.bat or whatever call winnt /b to copy the necessary files to a bootable FAT16 partition on the HD and eliminate the need for the floppies; using that approach, you'll be running Setup from the HD, not from the CD though.
That wouldn't work because the boot floppies made in the NT 3.51 setup expect that all the files from the DOS portion of the setup to already be there. To make it bootable, you could add a DOS floppy and in the autoexec.bat run the setup after loading a few CD drivers.
That won't work. The DOS part expects you to create three floppies, and A: will be an emulated read-only floppy. The only way I see something like this working is somehow using memdisk to emulate a hard drive, and writing an NT driver to read it while in protected mode (as memdisk only traps BIOS calls).
It'll work if you use a DOS boot disk as the boot image file and then have autoexec.bat or whatever call winnt /b to copy the necessary files to a bootable FAT16 partition on the HD and eliminate the need for the floppies; using that approach, you'll be running Setup from the HD, not from the CD though.
I didn't know about that switch, thanks. It should be possible to copy those files to a CD, then add a few CD-ROM drivers and an NT 4/5 loader (please correct me if I'm wrong).
I just tried the following (using the three floppy disks) I simply used Winimage to expand first one to 2,88 Mb, then copied SOME of the files of the other bootdisks and deleted SOME others.
Final result was this:
Quote:
Il volume nell'unit… J Š NTWKS35A_01 Numero di serie del volume: 0CEA-183D
Basically I deleted all SCSI drivers that won't be used.
This 2.88 floppy boots allright in Qemu, thus it should also work when used as an El-Torito emulation image in a .iso.
I cannot say whether it would work on a "real" machine due to missing drivers, as said before one has to try and if needed check the bearwindows page I linked before.
If I remember correctly, someone made a bootable iso of daytona back in the osba days, is that here on any of the servers, perhaps you can check on how it was made bootable.
Namronia wrote:
i think "they" took the IMA file of the first floppy and put it onto the cd bootable with somekind of "ultraiso" or something like that
That was me that made the full ISO of Daytona 756 bootable...
I made my own bootdisk using an IBM dos bootdisk, from memory, using
any MS-Dos version just gave errors of some sort whereas the IBM Dos
didn't, I think it had something to do with memory managers or the like
when attempting to install using the winnt /b command, but that just may
have been a problem relating to that build anyhow...
If you'd like I could extract the bootable image I made from the ISO &
post a D/L link here for it...
If it worked on a beta I'd imagine it to work on a retail..!
I have got it to successfully install now through CD Boot! I have used 2.88MB Floppy Emulation to do the trick. The only limitation is that it can only see the "IDE/ESDI Disks, BusLogic Disks and Sony CD-ROM Drives (WormSony)".
Code:
1 System Processor [65600 Kb Memory] MultiProcessor Kernel
Restart and set the recovery options in the system control panel or the /CRASHDEBUG system start option. If this message reappears,
The cause of this stop error is that the Kernel cannot find the native application it needs, SMSS.exe or the User Mode System DLL (NtDLL).
The Windows XP Equivalent of the error message:
Code:
STOP: c0000221 Unknown hard error. \SystemRoot\System32\ntdll.dll cannot be found.
The thing that troubled me for some time was the GUI Setup. It also needed several tag files, specifically, disk101-disk103, disk1.w-disk32.w. It gives a non fatal error about CPPInstall, errno 5.
The ISO is uploaded to the BA FTP.
Enjoy! It has SP5 integrated, even though NT does not say it.
Post subject: Re: Windows NT 3.51 CD Boot Problems Posted: Mon Mar 26, 2012 11:13 am
Joined Thu Nov 01, 2007 2:29 pm
Posts 42
Should this be of any use, it has been recently found how you can have bigger than 2.88 Mb floppy image in the El-Torito floppy emulation image. Details are here: http://www.msfn.org/board/topic/152399- ... emulation/ Basically you can have a superfloppy as big as: 0x03: 1024*2*36 * 512 = 37,748,736 0x02: 1024*2*18 * 512 = 18,874,368 0x01: 1024*2*15 * 512 = 15,728,640 This would allow to have the "full" set of floppies.
Users browsing this forum: No registered users and 14 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum
All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.