kof94

I disagree but that's not the point. I read this article sometime ago and it kind of sums up the whole Windows/Linux divide as far as I'm concerned.

Syslinux/isolinux, is free, highly configurable and in active development and theres a guide here. Enough said .

My first suggestion would be to try another VM to see if you get the same issue. I use QEMU and VirtualBox if that helps. If all else fails burn a copy to a CD/DVD-RW and test on a real machine.

Yep, all the info you need is already in this forum. First read the stickies then post if you stuck with anything specific. XP, Ubuntu and System Rescue CD are all covered in the isolinux sticky started by jetman.

Well done, glad we could be of service .

No problem B)

I don't own a copy of Vista so I can't really help with this, however, the version of isolinux.bin in the syslinux 3.52 package is broken and not Windows friendly. Rollback to the version from the syslinux 3.51 package and see if it helps.

I don't use Ubuntu any more but I forgot to mention you also need the '.disk' (hidden in linux) directory on your disk as well. This might be a silly question but you do have the livecd version and not the console based alternative cd don't you?

Yep. If you need captive ntfs driver support for DOS with read/write access and LFN then you would need to pay for the professional version of NTFSDOS from Winternals (now owned by Microsoft).

It's now maintained by Avira and you can get it from here.

This might not help because I don't have Ghost 11 but I know that some previous versions were based on Win/BartPE which is fairly easy to add to your disc. If this is the case then all you need to do is search this forum. If not then you might be able to turn your floppy discs into a CD.

It may pay to ask this question in the WinPE forum but as far as I know winbom.ini can only be at the root of your disc. The only way I can see you getting round this is to see if there is any reference to it in setupldr.bin and/or txtsetup.sif and edit the name or location of the file. Apart from this you can rename your I386 dir to something else with four letters. So, instead of... ... you would just rename your I386 dir to OPK1 CDROOT\OPK1\ The simplest way to learn how to do this is to read the BartPE section in Flyakites Guide . I hope this helps. -kof94

Hmmm, the ini that comes with that package is preset so I'd say it isn't cdimage, you could try mkisofs to see if that makes a difference though. I use VirtualBox everyday on my Linux box to test my boot disc and I haven't had any problems, however, a virtual machine is no substitute for a real machine when it comes to testing. Could you post your disc structure and your isolinux.cfg please, then we can see if this is just a config error or not? -kof94

Or just grab CDImage GUI from here, it comes preset to the most commonly used settings . Also (as Jet stated way back) don't use isolinux.bin from the syslinux 3.52 package if you intend to add Windows XP (or any NT family OS) to your disc. You'll just get an annoying error message when loading the boot sector! Use the one from 3.51 instead.

Depends on how you implement it but which ever way is good for me. Sounds good . I can wait.

Yep! Yep again . This is basically how WPI does it with gcond/cond. Although you might want to change it to 'IfExists' not 'IfNotExists', that would defeat the point . You could always add both though, which would be better. If you add these functions I think I'll more than likely switch from WPI to Mars Installer instead. One final thing, if you're considering adding a graphical editor please provide it as a separate app. One of the main reasons I like Mars installer is because of it's size, there's no need to bloat it with such a tool. Well, thats my opinion anyway.

@Marsianin I'm glad to see you decided to add dependency checking although could you refine it slightly. At present (going by your example) if you unselect .NET Framework, Paint.NET becomes locked (greyed out). Could you change this so that if you unselect .NET Framework, Paint.NET just becomes unselected as well and the reverse if selected. Also, would you consider adding the ability to lock out (grey out) items already installed through an 'If Exists' system. I know I've asked this before but it's such a useful feature to have. Thanks -kof94

I know what your talking about, there's a similar image at bootdisk.com. Basically your looking at the most minimalistic DOS boot disk you can have that has no drivers or TSR's to screw up your BIOS flash. I'm afraid that if your BIOS doesn't support a SATA to EIDE bridge (SATA devices appearing as EIDE) then your gonna have to load a driver. Thankfully one does exist although I have had no experience with SATA CD/DVD drives so I can't comment on how good it is. Your first port of call should be to the NwDsk project site. NwDsk is basically a modular boot disc that you can add or remove different cab files to load different drivers and utils during boot. All you need is the cab file that contains the sata drivers. If you want to test this out first download the Ultimate Boot CD and boot the FreeDOS boot disc from the Boot Discs menu (note: this may fail also if isolinux can't see your drive either). During boot you should see the SATA drivers loading I hope this helps some how. Good luck. -kof94

What exactly does this have to do with multi-boot CD/DVDs??? If your going to spam at least choose the right forum .

Bookmarked. I just skimmed the article and it looks like a good read .

Sorry, I didn't mean to get on your case like that. I just hate to see someones work put down when all their trying to do is create something to benefit others without asking anything in return. I'm sure this wasn't your intention though .

No, but as ale5000 has stated... I think you can cut nitro322 a little slack though considering the amount of archives and installers Universal Extractor will extract from .

The boot sector (in your case boot.dat) points to setupldr.bin! The only editing required on the boot sector is hexing it to point to your setupldr.bin which must be placed in a folder no longer that four characters long at the root of your disc, hence the reason why you would create a boot folder. I think you need to go back and read the whole of Flyakite's guide and experiment.

Well I feel really confident now . You're soooo sensitive.... You'e probably already seen this in your travels, but I think it mite be time for a new .signature.....Jet We are debian.org. Lower your prices, surrender your code. We will add your hardware and software distinctiveness to our own. Resistance is futile. Debian sounding more like the Borg or should I say M$.

deleted