نعم يمكنك جعل لعبتك التي قمت بصناعتها من RPG Maker
إلى جهاز الدريم كاست
الموضوع منقول من أحد المواقع الأجنبية التي لاأذكر من إين حصلت عليها
وهو غير كامل.
الموضوع بالكامل بالإنكليزي <<<لم أقم بترجمته
لأنه غير كامل و السبب الحقيقي (ماعندي دريم كاست)
يعني ماجربته يستوي وله لأ
وهو لإصدار RPG Maker 2000 ولا أدري أن يعمل على 2003
المهم نبدأ
RPG Maker 2000 Games on the Dreamcast
Table of Contents:
I. Overview
1. Foreward
2. What you need to have..
3. Certain Parameters your RM2K game must meet...
4. Current Bugs/Things that won't work...
II. Procedure
1. Setup/Procedure
2. The self booting tutorial
III. To be continued...سيتم أكماله لاحقا
I. Overview
1. Foreword-
This FAQ is designed to expand your RPG's horizon and allow you and others to play your
RPG on the Sega Dreamcast console. It is proven that it WILL work (maybe not perfectly)
but it will work on the console. I have successfully played 2 games on the Dreamcast,
Mr_Haze's Runic Legacy (Though the battles don't work very well) (Don't have the URL
right now, sorry...) and Lysander86's A Blurred Line (get it from www.phylomortis.com
under "Advocate's Choice", and grab Phylomortis I and II while you're there.) I hope you
can get this to work, I've tried hard on perfecting the technology. Good luck
2. What you need to have-
You'll need the following things to even attempt to do this (or at least, I think, there
may be other ways..). You need:
1. An RM2K game that meets the parameters listed in the section "Certain parameters
your RM2K game must meet..."
2. A Dreamcast Console (Of course.)
3. A CD Burner and blank CD (NO CD-RW).
4. Nero Burning Rom,or Easy CD Creator
5. A Dreamcast Boot CD *As of right now. I'm working on a self booting version. There
is a version of a Self-booting CD included in this FAQ, but I did not make that one, but it
is the one my Visual Basic teacher and I used to set up the game.* (files for this are
available for download at: www.dcemulation.com. Get these files, burn to CD and you
got yourself a boot CD).
6.Patience and some Kool-Aid. You'll need them.
3. Certain Parameters your RM2K game must meet-
1. ALL PICTURES MUST BE IN .png FORM. Do not import in .xyz!
2. Having 11 common events running at the same time will render the game unplayable.
3. LISTEN CLOSELY. When you make a gamedisk, DO NOT, I repeat, DO NOT got to "Add
RTP" or whatever. Open up your game's folder, and go to the rpg_rt.ini. At the very top,
copy/paste this line (without quotations) - "FullPackageFlag=1" What this does is
automatically with "Add RTP package" while making gamedisk doesn't work. Make sure
that all the RTP files you used are registered in the database, and is in the correct
folder.
4. Current Bugs -
1. Midi will not play, I don't know why, but someone on the original post mentioned
something about a midi player not available, but I don't think that'd be it, since the DC
runs on Windows CE, that's the main reason it is possible. 2. Having 11 or more
common events running simultaneously will render the RPG UNPLAYABLE. It will move so
slow, that the game will just freeze up eventually.
3.Using a CD-RW sometimes meeses up
II. Procedure
1. Procedure (This is the simple part). -
Make a gamedisk, and decompress it to a base folder on the main drive. Example, your
game's name is "DarkMatter Rocks", make a gamedisk, and using WinRar
(www.winrar.com), decompress the .Izh file to a folder like C dmrocks\. Make sure
when you open the folder you can see the files, and not another folder like "dmrocks".
Example, when you open C dmrocks\, you see the rpg_rt.ini file and make sure it looks like this:
[RPG_RT]
FullPackageFlag=1
GameTitle=DarkMatter Rocks
MapEditMode=0
MapEditZoom=1
Ok, it get's a bit harder. You need an audio track. The easiest way to do this is to open
Sound Recorder with no microphone hooked in, and record for up to 10 seconds It MUST
be 4 to 10 seconds and it must be some sort of audio file like "wav". Place this file in the
directory with the rpg_rt.exe file. Got that? Ok, now take a random midi and rename it
to a random 8 digit number,just do not repeat 2 in a row. Example: 56743567=
correct.
56743367= wrong.
Now the filename must have "xa" somewhere in it. Example: You could have
"45674232.xax" if you'd prefer a 3 letter filename, or you could just use 12345678.xa.
Put this file in the smae place as you put the audio track.
Simple enough, eh? Now I'm hoping you are a little bit experienced with your CD
Burner. Make an .iso image (compressed CD images) of the files in your C dmrocks\
folder (or whatever that you made it). Burn the .iso image to a NEW CD, and don't use
CD-RW's, remember that. Check the contents of the CD, it should be decompressed. If it
isn't decompressed, then burn the folder with .exe protection off. (Some CD burning
software won't allow .exe's to be burned...) You've gotten this far, the rest is just plain
elementary. I haven't used Boot CD, but I expect that it'd be quite simple. Stick the
BOOT CD in, and switch, ask Shapyi on the message boards, I think he's experienced with
the Boot CD and maybe he'd write an FAQ.
III. To be continued...سيتم الإكمال لاحقا
There's a lot of stuff I want to discuss, like different concepts and
stuff, but I'm sorta pressed to release the FAQ. Look below for dcemulation's self boot
CD, and see if you can get your computer teacher at school to help you, I got my Visual
Basic teacher to help me.
Selfbooting Dreamcast CD-Rs:
Before you read:
This guide is designed for people who are trying to burn the various emulators and neat
little programs. (Mainly found on www.dcemulation.com) It is NOT for people who are
trying to burn illegal Dreamcast games. I do not condone such activity, and I will not
help anyone who tries to do it. Repeat: THIS IS FOR LEGIT SOFTWARE ONLY. For this
does not explain how to rip down CDDA tracks on a CD-R.
Basic Idea:
For a CD-R to be bootable on the Dreamcast, it must have the correct structure. I know
this is well known, as well as the structure itself, but I figured I'd write it down a little
clearer for everyone. Also , this guide is for WINDOWS USERS. Everything in it is tested
on a Win 98 machine, and can only be confirmed to work on other Win 98 Machines.
Initial Basic Structure:
First, the CD-r has two sessions. The first, must be an audio track. This track
MUST be at least 4 seconds long, but it can be longer. This First audio track is what
would be equivalent to the "Disk warning" message found on standard GD-ROM disks.
Because of this, I recommend getting your MIC out and recording a "Disk warning"
message. The second track has to be a CD/XA track, and must contain a regular
ISO9660 File system. Notes on how to create this will come later in this document
Tools:
For making my personal self-boots, I use a combination of several programs. For the
actual burning process, I use two EZ-CD Creator 4, and the Win32 version of CD Record.
EZ-CD Creator came with my CD Burner, and most burners today come withit as well. If
yours didn't, you can attempt to use your unrner's program, but I can not guarantee it
will work. Still, if you would like to try to use another program besides EZ-CD, I will
detail which options you should look for in your program. I'm sure EZ-CD isn't the only
one that will work, it's just the only one I've tested at this point, so feel free to
experiment. As for CD Record, it is included in the zip file that the text file you are
reading now should be found it (along with other needed programs)
The First Session (Audio Track):
Before you go on here, and to eliminate any confusion, go to a MS-DOS prompt,
navigate to the directory where you have CD Record (most likely C selfboot) and type
this at the command line:
cdrecord -scanbus
The program will show you a list of all attached SCSI, ASPI, and/or MMC compliant
drives on your system. Look at this list carefully. It's seperated with sets of 3 numbers
that correspond to your CD burner. In Windows 98, on a standard machine, this is most
often either 0,0,0 or 0,1,0. After you get these numbers, remember them. Write them
down if you have to, they will be henceforth refered to this document as "x,x,x" so
wherever your SCSI ID should be, you'll see:
-dev=x,x,x
Ok? Understand? Good.
If you personally are happy with 4 seconds of silence as the first track of your CD-R, I
have included a 4 second .raw file in the zip. If this is what you plan to do, just
insert a blank CD, and type:
cdrecord -dev=x,x,x -multi -audio audio.raw
You can skip to the second section now if you wish, on burning the second session.
Because the rest of this section details how to create a custom "disk warning" track.
Ok, like I said before , you need at LEAST 4 seconds for the audio track. We all know
this, we've read it before. Well, after burning several emus for friends and such. I got to
wondering about that 4 seconds of silence that plays when you put one of these CD's
into a standard CD player. Sure enough, my hypothesis was correct. This is the same
thing that would be played off a GD-ROM if you put it into a standard CD player.
Normally , I used CD Record for the entire selfboot process, as that was what all the
tutorials told me to use. But I, personally don't know much about CD Record , so when I
decided to make something different then that silence, namely YOU saying "This disk is for use
only on Sega Dreamcast", or "What the hell are you doing with my CD? Give it back to me
now", or even some kind of Greetz if you plan on giving a lot of CDs out to friends, all you
have to do is get out your computer MIC, and record yourself a .wav file saying whatever
you want. The only stipulation is that you MUSt record 4 or more seconds in your .wav
file. That's it. Mine usually go about 5 or 6 seconds, it's really irrelevant.
Something you may or may not find interesting, because of the complex structure of a
standard GD-ROM, the first track of audio on GD-ROMS is limited to a few minutes
maximum. This is not the case with CD-Rs. A lot of people use those "dummy" files to
make that first audio track REALLY long. For instance, one REALLY long .MP3 mix of
several songs you like. It makes no difference, as long as it's only ONE track. It may be
possible to have more, in fact it probably is possible, vut as I haven't tested that, I
won't recommend it.
So now that you have your "Disk warning" wave file, or your MP3 of "the perfect
drug" (sounds a lot cooler anyway) fire up EZ-CD Creator, and start a new Audio CD
layout. Browse to your audio file that you intend to use as the audio track, drag it into
the bottom window, and then click "Create CD" to burn it (make sure you put a blank
one in, duh) When it pops up the Dialog box after you press "Create CD" make sure that
the radio buttons next to "Close session and leave CD open" and "track at once" are
selected. Then go ahead and burn it.
The Second Session (Data Track):
Now that you have your "CD Warning" track burned, as always with self-boots, you need
to find out the off set number for your ISO9660 file system. To do this, make sure the
CD with your audio track is in the burner. Then go to a DOS prompt, navigate to the
directory where you have CD Record (probably C selfboot) and type the following
command:
cdrecord -dev=x,x,x -msinfo
(Where x,x,x is YOUR CD burner's SCSI ID, that you got from CD Record earlier)
When you press enter, CD Record will spit back at you 2 numbers. A zero, and then
something which will be different depending on how long your first audio track is. The
format will be like this:
0,8253894
these are your offset numbers.
The 8253894 above could be any number. Just make sure when you scan for
Multisession Info (the -msinfo argument) that you write down YOUR offset numbers
EXACTLY as they appear. You will need these when you make your ISO9660 image, and
possibly when you run Binhack.exe. (which is the next step) these numbers will here on
be referred to as x,yyy (I made it yyy to remind you which one is longer, some of my
friends have had problems with that, so I figured some of you might as well)
***Special Note: IT_IS_possible that the program you are trying to burn will have an
executable that is NOT called 1st_read.bin. Most of the time it will be, but in case it
is not, simply substitute the name of the executable file in the document where ever
you see first read.bin***
Before you proceed, you will now have to make a directory with all the files needed by
the program you wish to burn in the same directory that the mkisofs.exe program is.
(again, most likely C selfboot) You can call this directory anything you like, as long as
it's 8 characters or under. The Echelon Selfboot Tutorial suggests you call the directory
simply "data" which works fine. Just put all the files in the "data" directory (or whatever
you name it) the "data" directory should contain the 1st_read.bin in the top level, and
any other directories or files.
The ip.bin file may also be in this directory. If it is, move it one level up, so its in the
same folder as the mkisofs, cdrecord,,binhack, ect. programs. Also, one final step before
you continue, ove(not copy) the 1st_read.bin file one level up as well , so the ip.bin
and 1st_read.bin files are in the same place. The reason you move and not copy it
is that you're just going to move it back, so you would just overwrite the old one
anyway. By the way, I suggest you make copies of all the original files before you even
attempt to make the selfbooting CD-R. that's just common sense, in case you screw
something up on accident.
Anyway, now you need to configure the ip.bin and 1st_read.bin files so that your CD-R
will boot correctly. To do this, go to a DOS prompt, navigate to your selfboot directory
(you BETTER know where this is by now) and type:
binhack
The program will run, and it will ask you for the name of your executable. Type
1st_read.bin. Then it will ask you for the name of the boot sector. Type ip.bin. If your
program is based off the Windows CE development kit, it will not ask you for the off
set number, but if it is, you will have to input ONLY the second number of your x,yyy off
set numbers. For example, if your x,yyy numbers were 0,1234567 you would put in
ONLY 1234567. After this is done, you will have your hacked ip.bin , and hacked
1st_read.bin. Now you can move the new hacked 1st_read.bin file back to your "data"
directory. You are now ready to make the image to burn.
To do this, go to a DOS prompt (...you know where) and type the following:
mkisofs -C x,yyy -V zzzzz -I -o data.iso data
Now, some explanation of the above command. Where the x,yyy is, you should put
YOUR off set numbers. Where the zzzzz is, you can type any label you want for the CD,
just keep it under 8 characters. Where it says data.iso, you can technically put any
name you want, but to keep it simple, and to make this document work well with the
Echelon tutorial, I have kept it as data.iso. And lastly, that last part, where it simply
says "data" is the name of your "data" directory. Like I said previously, you can call this
whatever you want, meow, assbite, ect. Well, whatever you named YOUR "data"
directory is what you should put here. So, if you put "data" there and you named the
directory where you put the files for the DC program you're trying to burn in a directory
called "pigfukr", it will give you an "invalid node" error. Just keep this in mind when you
name your directory.
Wow, now..after all that is done, you will have an ip.bin and a data.iso (or whatever you
named it) in your selfboot directory. Now it's time to patch that ip.bin into that data.iso
you made. How you do this, is once again open a DOS prompt (yes, go there... you know
where...go..) and type:
ipins
The program will ask you for the name of the bootsector. You will type ip.bin then it will
ask you for the same name of the ISO. You will type data.iso(or whatever you named it) now
you are FINALLY ready to burn the final session.
To burn the second session, got to a DOS prompt (this is the last time) in your selfboot
directory, type:
cdrecord -dev=x,x,x -xa1 data.iso
Make sure that the x,x,x above is YOUR SCSI ID, and that "data.iso" is actually the
name of the ISO YOU made. After the disk is burnt, if everything went fine, you should
now have your selfbooting Dreamcast software,complete with personalized "disk
warning" message. Enjoy!!
أنتهى الموضوع أرجو أني قد أفتكم بشيء
