Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About midz

Contact Methods

  • Website URL
  1. Have you tried using the mkisofs command line Jotnar suggested to me back then? It worked fine for me, you can find it back there, anyway just in case this would be it: mkisofs -J -joliet-long -no-iso-translate -N -V mb12 -b boot/isolinux/isolinux.bin -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o mb12.iso \mb Would like to know if this does the trick for you.... midz
  2. Jet, you were right I was using the same layout for slax6 as for slax5 and as you know it didn't work. I tried doing it your way with the boot and slax dir under a slax6 dir and it worked with: from=/slax6 What did you mean by 'from=' changed a little bit? Here's the interesting part, BT3 works with the usual layout, boot and data dirs split, BUT using Jotnar's mkisofs command line (Jotnar, can you expand on why this works...), I'm guessing this has something to do with the file system since my initial one used rock ridge while the new one uses joliet? Funny though i expected BT3 to behave like Slax6, guess i was wrong. Thanks, midz
  3. this is the mkisofs command line i'm using mkisofs -N -V mb12 -b boot/isolinux/isolinux.bin -d -iso-level 4 -no-emul-boot -boot-load-size 4 -boot-info-table -o mb12.iso \mb
  4. Yeah, my bad, i missed the from= parameter i was using on slax BUT no good it still doesn't find it's data directory as discribed in my earlier post, i can't understand why because slax works and the config lines for slax and bt3 are essentially identical as you can see... LABEL slax MENU LABEL ^7 Slax 5 KERNEL /boot/slax/vmlinuz APPEND vga=769 max_loop=255 initrd=/boot/slax/initrd.gz from=/slax init=linuxrc load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=4444 root=/dev/ram0 rw nopcmcia ----------- LABEL bt3 MENU LABEL ^8 BackTrack 3 KERNEL /boot/bt3/vmlinuz APPEND vga=0x317 max_loop=255 initrd=/boot/bt3/initrd.gz from=/bt3 init=linuxrc load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=6666 root=/dev/ram0 rw autoexec=kdm Also livecd.sgn is in the bt3 folder. Am i missing something? Thanks, midz
  5. i'm having a problem and i can't seem to solve it, hopping someone can help. i'm trying to integrate Backtrack3 (or 2 - it has the same issues) into a multiboot dvd based on jets initial post, bt3 boots fine until *looking for data directory Fatal error occurred - BT3 data not found. You are maybe using an unsupported boot device (eg. SCSI or old PCMCIA) ... i have no ideea why this is happening since bt is based on slax and slax works perfectly in this setup. dvd directory structure is: \dvd\ boot\ bt3\ dsl\ isolinux\ slax\ sysresccd\ bt3\ dsl\ i386\ slax\ sysresccd\ bootsect.bin WIN51IP WIN51IP.SP2 i386 is bartPE, config file snippet for bt3: LABEL bt3 MENU LABEL Backtrack KERNEL /boot/bt3/vmlinuz APPEND vga=0x317 initrd=/boot/bt3/initrd.gz ramdisk_size=6666 root=/dev/ram0 rw autoexec=kdm testing done in vmware - virtual cdrom device using ide interface i have to admit my isolinux skills don't go higher than begginer level so i'm running out of ideeas, googled it and what i found didn't help me, please help... midz
  6. Nevermind my last post I'll answer my own question, cd identification files WIN51IP and WIN51IP.SP2 need to be in the root of the Super-Disc next to BOOTSECT.BIN, now it runs fine. Onto adding Slax... anything I should pay special attention to when doing this? Thanks jet again for sharing your experience, much appeciated
  7. Thanks jet, you were right, using bootsect.bin did get it to boot BUT now when it gets past "Setup is inspecting your computer's..." i get: "Please insert the disk labeled Windows XP Professional Service Pack 2 CD into drive A: Press Enter..." this is exactly the same screen I got when trying to use BartPE with BCDW 2.01a Any thoughts on why this happens, could my SP2 not be slipstreamed "properly"? *BartPE iso works fine on it's own
  8. Back again, my bad for overlooking the link you provided for creating a multiboot dvd using diffrent xps, but I do belive you integrated BartPE into your dvd before that probably using a diffrent method, so here's what i've tried: Judging by the KERNEL statement in your first post regarding BartPE/XP I assumed you were not using the standard directory structure described at the begining of this thread so I placed I386 and Programs folders from Bart in the root folder of the Super-Disc, I also placed SETUPLDR.BIN in the root folder resulting in the following directory structure: C:\Super-Disc\ boot\ isolinux\ dsl\ sysresccd\ sysresccd\ dsl\ I386\ Programs\ SETUPLDR.BIN *I didn't edit anything in SETUPLDR.BIN since I386\ was present in the root directory with the default name and added this to ISOLINUX.CFG LABEL bartpe MENU LABEL ^BartPE/WinPE MENU DEFAULT KERNEL /SETUPLDR.BIN the iso image boots fine in VMW but when I select BartPE it goes to a black screen and a blinking cursor and it stays there I don't know if this is a completley wrong method because there's something I don't undrestand, if so can you give me a guideline? if the method is ok can you help trubleshoot any steps I'm doing wrong? Thanks, midz
  9. Thanks jet, didn't mean to be rude or out of line and hide behind the beginner status, I did read the first 6 pages of the thred, actually i read the first page at least twice and I also built the dvd and tested it in vmware(before I posted the first question), it worked fine except some problems with zen, anyway I also tried inserting BartPE by myself (based on your tip ) but I couldn't get it to run, BartPE entry apeared in the menu but when I selected it nothing happened. That being said I guess I'll try again and post a description of the process, maybe you can help troubleshoot. Again sorry for being out of line.
  10. Can you detail the process of integrating BartPE/XP in the multiboot dvd? Beginner question, i know, but i'm new to multibooting stuff and kind of lost. Thanks