Search the Community
Showing results for tags 'multiboot'.
-
Precursor: *SKIP IF UNINTERESTED* I have a multibooted computer with 13+ entries in the bootloader. Currently, they go as follows: Win 11, 10, 8.1, 7, Vista, XP, 2K, NT 4.0, ME, 98 SE, 95, 3.1, and an Ubuntu install. All of them boot correctly (now after much disarray), and are neatly put into a single boot menu running without metro UI but on the modern BCD framework. I use 5 real mode boot sectors for ME, 98 SE, 95, 3.1, and Ubuntu using modified versions of generated files from easy bcd (based on grub4dos 0.4.6a). For NT 4.0, 2K, and XP, I also use Easy BCD (this time unmodified) to boot into them. Each operating system works fine. All operating systems above 2K have fully fledged drivers for everything, the base board is an IPIBL-LB (random HP board) with 4 drives + a CD drive. *** SKIP TO: Here's the problem: If I follow these steps, things go wrong: Boot into NT 4.0 (no issues) Restart (no issues) Boot into Windows 7 (no issues*) Once into Windows 7, after fully started, Windows 7 (but not any other operating system [ex 8.1]) will become super sluggish and slow. All drives are accessible except for the ones accessed by NT 4.0 during its boot (any time in the past, even hundreds of power cycles ago), mainly NT 4.0 itself as well as Vista and 2K. The FAT (non NTFS) drives accessed by NT 4.0 remain accessible, but NTFS drives accessed become unreadable/uninitialized in only windows 7. Trying to start a disk check on those volumes fails, and the UAC prompt takes forever to come up anyway. The system is unable to shutdown too. The current only way to fix this is to boot into another operating system and disk check anything accessed by NT 4.0. Here's what I want: Windows 7 can access all drives and not be sluggish after booting into NT 4.0 any time in the past Windows 7 can still see all partitions on all drives Here's what I don't care about: NT 4.0 not being able to see any other partition (actually ideally it shouldn't be able to) Here's my idea: NT 4.0 does not have disk drivers. It sees the drives (500+ GB) as 131 GB (No lba 48 support) - I have a disk driver I could install, but doing so seems redundant since it will only be a nightmare to reletter each drive and fix the USB drivers as well as making more partitions accessible from NT to further break 7 - If I could maybe get Vista to unletter from NT 4.0 and install NT on FAT, then it would maybe fix the issue? However I can't unletter Vista. I would also need guidance on installing NT 4.0 on FAT. Other than that I'm clueless Other info: I have removed all drive letters from NT 4.0 besides itself (now C:) and Vista (Z:) (it won't let me remove Vista as "boot drives MUST have letters" [this makes me confused]) NT 4.0 can only see 2 drives (technically 3 but it doesn't read the third), of which the picture has the layout. The full disk manager layout from 8.1 can be seen as well. This is NT 4.0 built 1381 SP6 I would really appreciate some guidance! I'm lost. Genuinely no idea where to start or how one or two partitions ruins 7 completely. Clueless, however much I might know. Sincerely, RU-B **Don't want any "Give up" vibes please**
-
I've used WinBuilder (Win8.1SE v82) to build a custom PE/RE multiboot USB and I've added 4 ISOs to it and installed grub4dos (tried with bootice as well as RMPrepUSB), however I cannot get certain ISOs to boot as they hang at: (hd0,0) FAT12 BPB found with 0xEB (jmp) leading the boot sector. probed C/H/S = 80/2/18, probed total sectors = 2880 I've searched for hours on Google, however I can't find anything that references the cause of this. I'm getting this error with a custom repair iso, and gparted (most recent amd64) is hanging, eventually kicking back to bootloader command line after ~5min or so. PartedMagic (most recent from 2015.05.04) boots fine, as does the Comodo Rescue ISO. The Win8.1SE build is setup to boot to BCD with an option for Win8.1SE, WinRE, and grub4dos. Grub4dos then has several entries, 4 of which are ISOs added during the build. All menu.lst entries are mapped to (hd32), which would be right for a CD and I was curious if this would be the cause of the issue since it's a flash drive. I've tried partitioning the flash drive every which way, both through Win8.1SE and RMPrepUSB, but I can't seem to get gparted and the custom recovery iso, which contains both dos and linux utilities, to boot.
- 1 reply
-
- multiboot
- Bootable USB
-
(and 3 more)
Tagged with:
-
With Windows XP finally reaching what is essentially a finalized state, I'd like to put together a "Final" CD for usage on old computers. So the challenge is, how can I shove XP Pro, Home, and Media Center onto a single CD (650 MB, 700 if you wanna push it), along with the latest updates(ideally OnePiece packs, perhaps minus Windows Search). I'd also prefer it if I could at least get Mass Storage and LAN drivers onto the CD, with WLAN drivers being an added bonus. Finally, I'd like to add in MrSmartyPant's OEM Activation to the XPs, for legal activation purposes only. Since WinNTSetup recently added support for XP from a WIM, I'm thinking it may be a good solution for compression. However, I'm not sure if it'll make up for the cost of throwing a PE onto the disc. Anyway, does anyone have any ideas how we can get all that onto a single disc?
-
Hi there, just try to use grub4dos and mkisofs to make my nlite-compiled XP-CD multiboot-ready. Problem: The Grub4Dos of the boot-record is looking for /menu.lst (written in lowercase!) but all files on the DVD appear in uppercase. Maybe this is because of some ISO9660-standard. Anybody knows what do I have to change to allow lowercase-filenames? Right now, the DVD is ISO9660+Joliet3. I'm sure grub4dos and/or mkisofs need some specific dvd-format at early state of boot-process. Propably grub4dos' search for menu.lst is hardcoded in the boot-record and not editable.
-
Install Win98SE from an ISO on a USB Multiboot Flash drive
steve6375 posted a topic in Windows 9x/ME
Hope you find this useful... An easy2boot USB drive will boot most linux ISO files just by copying over the linux iveCD ISO files. To add a Win98SE Install ISO, you need to delete all unnecessary folders and rename the ISO file to have the .isoDOS01 file extension. You can then boot directly from the USB drive and choose the Win98SE ISO from the menu. For more details see here. The same principle should work for most DOS-based Install ISOs (as long as you keep the files numbers down by pruning!).