Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: UAE4ALL Burning Tutorial

                  
   
  1. #11
    DCEmu Newbie
    Join Date
    Apr 2004
    Location
    Posts
    89
    Rep Power
    0

    Default Re: UAE4ALL Burning Tutorial

    it sure is

    You need to have the BroadBand Ripping Kit.whats that? i never needed that to make selfboot diskz

    tinku ???

  2. #12

    Default Re: UAE4ALL Burning Tutorial

    ... i am familiar with those different manners of making selfboot discs, but using bin2boot has got a huge disadvantage compared to the echelon method.
    You cant read the disc properly. Each time you want to grab files from that disc, you have to use isobuster and hope that its going to extract the files.

    Again...how can i build a disc using cdrecord and NOT bin2boot or suppn like that.

    The disc shall be readable afterwards....

  3. #13
    DCEmu Coder
    Join Date
    Apr 2004
    Posts
    227
    Rep Power
    74

    Default Re: UAE4ALL Burning Tutorial

    I've never had any problems reading a data/data disc...

    As for burning a disc with cdrecord, if you're doing it manually...

    Get a small audio sample, and burn that to a CD as an audio track
    Get the multisession info off the disc
    Create the second session using mkisofs
    Insert the IP.BIN into the second session image
    Burn the second session image using cdrecord

    Selfboot can do it though. Just choose the cdrecord method, and follow the instructions.

  4. #14

    Default Re: UAE4ALL Burning Tutorial

    ok this tutorial fits to UAE4ALL:

    Step.1 - Get your SCSI ID
    From a DOS prompt, in your selfboot directory, type the following command.

    cdrecord -scanbus

    Cdrecord will give you a list of all attached devices that it can identify. Locate your CD-Burner on this list. Write down the 3 numbers it gives you.
    For example, if your CD burner is at 0,1,0 write those numbers down, just like that.
    (See notes if you have problems here)
    From now on, these numbers will be used where ever you see the command: "-dev=x,x,x" where x,x,x are your device's SCSI ID numbers.



    Step.2 - Burn the First Session
    From a DOS prompt, in your selfboot directory, type the following command.

    cdrecord -dev=x,x,x -multi -audio audio.raw

    When CD Record finishes it's task, you will have successfully burned the first session and first audio track

    Step.3 - Getting Multi Session off-set numbers
    From a DOS prompt, in your selfboot directory, make sure your CD-R is still in the drive an type the following command.

    cdrecord -dev=x,x,x -msinfo

    When CD Record finishes it's task, it will print on the screen two numbers. a Zero, and most likely either the numbers 11700 or 11702 which are the most common off set numbers for a CD-R with nothing but 4 seconds of blank audio on it (which is exactly what the first session is)
    (see notes if you have read the general tutorial on making "disk warning" audio tracks)
    When you have the numbers on screen, write them down. The first one will always be 0, but the second one can vary depending on your burner, and the length of the audio track burned in session 1. These numbers will be referred to from now on as "x,y" and will be used in the burning on the second session, and possibly the creation of the selfbooting image. Keep this in mind.

    Step.4 - Setting up the files
    From Windows, create a sub-directory (folder) inside your selfboot directory. Name this sub-directory "data". In this new directory, copy ALL the files needed for the program you are trying to make self booting.

    1st_read.bin (scrambled bin). *
    kick.rom : amiga bios renamed. *
    df0.adf : Floppy disk image.

    Make sure you have ALL files in root directory e.g. c:\selfboot\data\files_go_here.
    The top level (i.e. the root of "data&quot should contain a file called ip.bin, and 1st_read.bin. You need to move your IP.BIN file from your data folder into your main directory. You do NOT want the IP.BIN in your "data" directory.

    Step.5 - Hacking the boot-up files
    Ok, i'm leaving this as a step for one important reason. To warn you NOT to try and running binhack on the UAE4ALL 1st_read.bin file. For those of you that make self-boots on a daily basis, you may be used to running binhack on all your ip.bin and 1st_read.bin files.

    Step.6 - Creating the Selfbooting Image
    From a DOS prompt, in your selfboot directory, type the following command.

    mkisofs -C x,y -V SOLDIAZ -l -o data.iso data

    Make sure that in the command, you substitute in your off set numbers instead of x,y.

    After the program is done, you will have a new file in your selfboot director called "data.iso"

    Step.7 - Injecting the boot sector
    From a DOS prompt, in your selfboot directory, type the following command.

    ipins

    The ip inserting program will run, and it will ask you for the name of the boot sector. You will type "IP.BIN". it will then ask you for the name of the ISO image. You will type "data.iso". After the program completes (doesn't take very long) you will be ready for the final step.

    Step.8 - Buring the second session
    From a DOS prompt, in your selfboot directory, type the following command.

    cdrecord -dev=x,x,x -xa1 data.iso

    after the program completes (this will take several minutes) you should have a self-booting DC CD-R of UAE4ALL. Eject the disk when finished, and try it in your Dreamcast. Have fun!! Note: This last step does not work for a lot of people, you can also use CDR Win to burn the iso, just burn the iso in regular Mode 1.

    taken from dcemulation.com and a bit modified

  5. #15
    DCEmu Newbie
    Join Date
    May 2004
    Location
    Haiti
    Posts
    87
    Rep Power
    0

    Default Re: UAE4ALL Burning Tutorial

    Damn seems like people are looking for way to complex method for people having problems burning those emulators. Stuff that is needed is pretty much just the files from the emulator release in 1 folder, add an IP.BIN file, the BIOS file,and the ADF files you want to try with the emu,all in the same folder. Then just use DIR2BOOT.EXE to selfboot the files that are into that folder. That's all. So far it worked for me each time.

  6. #16
    DCEmu Newbie
    Join Date
    Jun 2004
    Location
    Posts
    8
    Rep Power
    0

    Default Re: UAE4ALL Burning Tutorial

    Hello
    I did put the:
    ip.bin
    1st_read.bin
    kick.rom
    and some adf images in the sub.
    But it boots after the sega screen then i was wondering if i could put the adf. files into a folder like i do in dcastaway.

  7. #17

    Default Re: UAE4ALL Burning Tutorial

    Ok what is the name of the bios i must rename to kickstart, aren't there more then one atari bios'. Also could please message me on how or where to find the adf files i need to run the emulator. Help whould greatly be appreciated i have tried to burn this and ruined many cds.

  8. #18
    DCEmu Newbie
    Join Date
    May 2005
    Posts
    3
    Rep Power
    0

    Default

    hi!

    i put

    IP.BIN (of selfboot directory)
    1st_read.bin (UAE4ALL archive)
    kick.rom (was kickstart1.3)
    df0.adf
    and many adf files

    in a directory and started selfboot!!!

    i burned the cd and boot it up in dreamcast.

    the dreamcast and after the sega logo appeared and the it starts over and over again. it loops....

    any hints? ideas?`

    thx.

  9. #19
    DCEmu Newbie
    Join Date
    May 2005
    Posts
    3
    Rep Power
    0

    Default

    now i followed Soldiaz instructions ... the same result.

    dreamcast logo
    sega logo - consolevison-

    looping ...

    plz help.

  10. #20

    Default

    ok I am going to burn the new beta 1 release and I will post exactly the way I do it...hope it works :-)

Page 2 of 2 FirstFirst 12

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •