Topic: "NTDETECT failed" with image file made with BootDI plugin  (Read 182 times)

0 Members and 1 Guest are viewing this topic.

"NTDETECT failed" with image file made with BootDI plugin
« on: May 03, 2017, 09:46:33 PM »

ZYX

  • Code Baker
  • Jr. Chef
  • **
  • Date Registered: Apr 2017
  • Posts: 56
Because of the simplicity and uniformity of tests, I am currently using ISO files put on UFD which are chainloaded with Syslinux boot manager and memdisk. However, in my final build I would like to extract the content of ISO file to the folder on UFD and to avoid memdisk to get faster boot and/or larger available RAM.

The WimBoot plugin allows putting of extracted I586 folder from the ISO file into the root of UFD, here are its Syslinux lines:
  com32 chain.c32
  append boot ntldr=/I586/SETUPLDR.BIN

However, when I try the same with BootDI plugin, with extracted all files from the ISO to the root of UFD, I get the "NTDETECT failed" immediately on the begin of boot. Here are its Syslinux lines (the difference is only in the folder name):
  com32 chain.c32
  append boot ntldr=/I386/SETUPLDR.BIN

I tried "Patch setupldr.bin" option without luck.

Any suggestion how to get the direct boot of image file made with BootDI from UFD without using ISO mapping?

By the way, it would be nice if BootDI plugin has an ability to specify target folder for Image path, like WimBoot, because in that case I could put several image files on the same UFD. Currently, it is not possible with the hardcoded I386 folder.

Re: "NTDETECT failed" with image file made with BootDI plugin
« Reply #1 on: May 03, 2017, 10:28:36 PM »

Galapo

  • Moderator, Gena Baker
  • Grand Chef
  • *****
  • Location: Australia
  • Date Registered: Sep 2010
  • Posts: 1956
Any suggestion how to get the direct boot of image file made with BootDI from UFD without using ISO mapping?

One of the main things to make sure is that the file has to be contiguous on the drive.

Regards,
Galapo.

Re: "NTDETECT failed" with image file made with BootDI plugin
« Reply #2 on: May 04, 2017, 04:38:24 AM »

ZYX

  • Code Baker
  • Jr. Chef
  • **
  • Date Registered: Apr 2017
  • Posts: 56
The image file is contiguous on the drive. Beside, Ramdrive even doesn't start loading the file where its fragmentation could manifest. As I said, I get the error immediately after I start boot from the Syslinux menu.

I forgot to mention, but I think it was obvious that I have used bootsect.bin, not grub4dos.

Re: "NTDETECT failed" with image file made with BootDI plugin
« Reply #3 on: May 04, 2017, 03:10:11 PM »

Galapo

  • Moderator, Gena Baker
  • Grand Chef
  • *****
  • Location: Australia
  • Date Registered: Sep 2010
  • Posts: 1956
Beside, Ramdrive even doesn't start loading the file where its fragmentation could manifest.

Ok, that's good to know. :thumbsup:

I forgot to mention, but I think it was obvious that I have used bootsect.bin, not grub4dos.

Sorry for that. I'm a bit tired here at the moment. :embarrassed:

You could try Grub4Dos though. It works for me for direct booting.

Regards,
Galapo.

Re: "NTDETECT failed" with image file made with BootDI plugin
« Reply #4 on: May 07, 2017, 10:29:45 AM »

ZYX

  • Code Baker
  • Jr. Chef
  • **
  • Date Registered: Apr 2017
  • Posts: 56
Well, grub4dos is required to get boot from image file, but it is not enough - it is also important to use FiraDisk or WinVBlock, while Win2k3 Ramdrive doesn't allow that. I tried even ntdetect.com by Dietmar and ramdrive.sys from Waik that are used in WimBoot after modifying BootDI, but without success.

Here are some results with one old computer having only 512 MB RAM:

BootDI_NTFScompress_100%_Floppy_Bootsect_Win2k3RD_CAB+WimPack_Outside_ProgSystem: 99 MB
ISO: 168 sec, 141 (RAM) + 42.3 (B:) + 32.8 (X:) MB
IM_: cannot boot

BootDI_120%_Floppy_Bootsect_Win2k3RD_CAB+WimPack_Outside_ProgSystem: 67.6 MB
ISO: 131 sec, 132 + 38.4/38.8 + 11.8/191.9 MB
IM_: cannot boot

BootDI_120%_HDD_Bootsect_Win2k3RD_CAB+WimPack_Outside_ProgSystem: 67.6 MB
ISO: 132 sec, 128 + 36.4/36.8 + 15.9/196 MB
IM_: cannot boot

BootDI_120%_Floppy_grub4dos_Win2k3RD_CAB+WimPack_Outside_ProgSystem: 67.8 MB
ISO: 132 sec, 132 + 38.4/38.8 + 11.8/191.9 MB
IM_: cannot boot

BootDI_120%_Floppy_grub4dos_Win2k3RD+WimPack_Outside_ProgSystem: 192.9 MB
cannot boot

BootDI_120%_Floppy_grub4dos_WinVBlock+WimPack_Outside_ProgSystem: 192.6 MB
cannot boot

BootDI_120%_Floppy_grub4dos_WinVBlock_GZ+WimPack_Outside_ProgSystem: 77 MB
ISO: 126 sec, 133 + 39.4/39.8 + 11.4/191.9 MB
IGZ: 126 sec, 206 + 73.6/77.9 + 11.4/191.9 MB

BootDI_120%_HDD_grub4dos_WinVBlock_GZ+WimPack_Outside_ProgSystem: 77 MB
ISO: 126 sec, 128 + 37.4/37.8 + 15.5/196 MB
IGZ: 127 sec, 202 + 71.6/75.9 + 15.5/196 MB

BootDI_120%_Floppy_grub4dos_FiraDisk_GZ+WimPack_Outside_ProgSystem: 77 MB
ISO: 123 sec, 132 + 39.3/39.8 + 11.4/191.9 MB
IGZ: 123 sec, 205 + 73.6/77.9 + 11.4/191.9 MB

BootDI_NTFScompress_120%_Floppy_grub4dos_FiraDisk_GZ+WimPack_Outside_ProgSystem: 104.4 MB
ISO: 153 sec, 105 + 24.4/24.7 + 62.5/191.9 MB
IGZ: 155 sec, 206 + 72.6/76.9 + 62.3/191.9 MB

BootDI_NTFScompress_96%_Floppy_grub4dos_FiraDisk_GZ+WimPack_Outside_ProgSystem: 107.9 MB
ISO: 158 sec, 139 + 41.3/41.8 + 26.9/153.9 MB
IGZ: 171 sec, 244 + 91.6/95.9 + 26.7/153.9 MB

BootDI_120%_Floppy_grub4dos_FiraDisk_GZ+WimPack_Outside_System: 77 MB
ISO: 125 sec, 121 (RAM) + 10.8/191.9 (Z:) MB
IGZ: 127 sec, 198 + 10.8/191.9 MB

BootDI_NTFScompress_100%_Floppy_grub4dos_FiraDisk_GZ+WimPack_Outside_System: 107 MB
ISO: 157 sec, 134 + 31.4/159.9 MB
IGZ: 159 sec, 241 + 31.6/159.9 MB

I forgot to take a note about the available space on profile (B:)/system (X:) RAM drives in my previous tests (http://theoven.org/index.php?topic=2110.msg23313#msg23313), which is also important to determine which settings are the best.

 

Powered by EzPortal