Well I bought mine new around mid-2002-ish (possibly May or somewhere round that time). Is that too new you reckon?

...which of these fine specimens allows you to boot burnt/import discs? http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&category=11319&item=8136906357&rd=1 http://cgi.ebay.co.uk/ws/eBayISAPI.dll?ViewItem&category=11319&item=8136761910&rd=1 http://cgi.ebay.co.uk/ws/eBayISAPI.d...

*Sighs* Might as well continue finding this other version myself....

So, what does BurnerO think then?

You did? Eeeep! Guess it didn't alert me to your PM in the first place. Checked it out now, cheers.

Erm, this place, for starters. Skyhawk mentioned it in one of my threads a while ago.

I managed to grab it from somewhere, and when I try to use it, it asks me to choose a Selfboot Buddy INI. Now I know what INIs are generally and all, but how are SBB ones written out exactly?

Well, I tried it with a keyboard plugged in this time, but I still got the same effect, much to my chagrin. And I'm using the latest shareware version direct from 3D Realms' servers, so it should be a flawless effort...

I think it's still: mkisofs -C 0,0 -U -R -V NESTERDC -l -o data.iso Adjust it to your own parameters. The -U is for upper and lowercase characters and -R is RockRidge. Add -J after -R for joliet. But does anyone know what the real difference is and can you use them in combination. I always thought ...

http://www.swapmagic.me.uk

Or perhaps a SM expert could point out a more superior site for ickle moi?

I think it's still: mkisofs -C 0,0 -U -R -V NESTERDC -l -o data.iso Adjust it to your own parameters. The -U is for upper and lowercase characters and -R is RockRidge. Add -J after -R for joliet. But does anyone know what the real difference is and can you use them in combination. I always thought ...

You don't suppose this is the AR device that can boot burnt discs do you?

Intriguing.... does anybody happen to know the command line that SBInducer 4 automates when building an ISO? Perhaps I could replicate that except use Joliet options instead.

Seeing as both Selfboot and SBInducer like to burn everything in ISO9660 format instead, natch.

I was hoping for some actual swift help round here, but oh well... I just tested ROTT DC (burnt stand-alone and dummified) and that worked beautifully without a hitch. This was with both v1.0 and v1.0.2a. No keyboard was plugged in. And just the important files were burnt on the CD (no DOS exes or r...

Ah, I've managed to work out a method for a "patch-IP.BIN"-less selfboot burn... simply install the latest Selfboot Inducer, place all your files in a directory named "Inducer", and just easily go straight to the disc-burning options rather than tamper with the Inducer-related se...

I forgot to clarify in my initial post - yes, I am definitely using the shareware files here. At first I tried burning just the majorly required data files (DUKE3D.GRP, *.CON, *.DMO, DUKE.RTS, MODEM.PCK), and then I tried including all the original shareware files, DOS exes and readmes included. Nei...

All I get is the plain-text loading screen, then a blank screen from then on for eternity. And yes, I do have the required files in the right directory, and it was made using Selfboot (the plain Inducer-less equivalent of Selfboot Inducer, if you remember). Does it detect what's plugged into the con...

Now I've got another problem... why are there no selfboot kits/apps aimed towards CDDA-featured stuff?

Everything seems to be aimed at simple data-only burning tactics, but what about projects like DCTonic and QuakeDC where CD tracks can be involved?

I don't understand why apps like Selfboot modify the IP.BIN file everytime when burning a disc (presumably just to include the Consolevision logo at the beginning). Isn't it possible to manually perform all of its commands yet not make it change that file about?