Menu
▾
▴
linuxdc-dev
|
From: David W. <dav...@ia...> - 2002-03-13 05:35:11
|
> I'm trying to create a bootable linux CD and I can't seem to get it to > work. Is this a proper forum to ask about creating bootable CD's? > > I tried the master.sh and also followed the instructions on the mc.pp.se > site. I'm guessing it could be my burner? It's a Microimages backpack CD. > > I can boot from a CD my friend made me a few months ago using Nero I > think. I walked through the instructions twice on two seperate occasions and have never had any luck. I think I'm hung up on getting a good IP.BIN as I don't have any existing DC software to snag a copy from. I found a tool that claimed to make one, but the resulting disk doesn't read. I'd sure love to have a working procedure, too. Hard to develop code when you can't run it. :( Not that anyone will be interested in the stuff I'd be porting as it's all wierd amateur radio digital stuff. :) Is there any cheap sound input for the DC? I can get line level audio and I just need to sample it at 8KHz/16bit or such. Is there a cheap Maple device that does that? I bought my DC for software development and have never played a game on it. :) I have no idea what kinds of controllers are available for it--except for the cool recent puru puru posts, that is. I'm not sure if I can think of a use for vibration in my application. :) Cheers, David N0YMV |
|
From: Adrian M. <ad...@mc...> - 2002-03-13 08:25:15
|
On Wednesday 13 Mar 2002 6:38 am, David Willmore wrote: > > I'm trying to create a bootable linux CD and I can't seem to get it to > > work. Is this a proper forum to ask about creating bootable CD's? > > > > I tried the master.sh and also followed the instructions on the mc.pp.se > > site. I'm guessing it could be my burner? It's a Microimages backpack CD. > > > > I can boot from a CD my friend made me a few months ago using Nero I > > think. > > I walked through the instructions twice on two seperate occasions and > have never had any luck. I think I'm hung up on getting a good IP.BIN > as I don't have any existing DC software to snag a copy from. I found > a tool that claimed to make one, but the resulting disk doesn't read. > It can be done, I assure you! What is going wrong? Just coasters? Have you looked at http://www.fivemouse.com? It has some instructions too... > I'd sure love to have a working procedure, too. > > Hard to develop code when you can't run it. :( Not that anyone will > be interested in the stuff I'd be porting as it's all wierd amateur > radio digital stuff. :) > > Is there any cheap sound input for the DC? I can get line level > audio and I just need to sample it at 8KHz/16bit or such. Is there > a cheap Maple device that does that? I bought my DC for software > development and have never played a game on it. :) I have no idea > what kinds of controllers are available for it--except for the > cool recent puru puru posts, that is. I'm not sure if I can think > of a use for vibration in my application. :) > There is a microphone which I am trying to write a driver for. But while I have made some progress I haven't got anything actually working yet :-< > Cheers, > David N0YMV > > _______________________________________________ > Linuxdc-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxdc-dev |
|
From: Dave K. <re...@li...> - 2002-03-20 04:57:51
|
On Wed, 13 Mar 2002, Adrian McMenamin wrote: > On Wednesday 13 Mar 2002 6:38 am, David Willmore wrote: > > > I'm trying to create a bootable linux CD and I can't seem to get it to > > > work. Is this a proper forum to ask about creating bootable CD's? > > > > > > I tried the master.sh and also followed the instructions on the mc.pp.se > > > site. I'm guessing it could be my burner? It's a Microimages backpack CD. > > > > > > I can boot from a CD my friend made me a few months ago using Nero I > > > think. > > > > I walked through the instructions twice on two seperate occasions and > > have never had any luck. I think I'm hung up on getting a good IP.BIN > > as I don't have any existing DC software to snag a copy from. I found > > a tool that claimed to make one, but the resulting disk doesn't read. > > > It can be done, I assure you! What is going wrong? Just coasters? Have you > looked at http://www.fivemouse.com? It has some instructions too... I've killed about 8 cd's and had to quit when I ran out. :) I used an IPBIN file from I think fivemouse.com and one from DCquake. Does the IPBIN and firstboot file have to be created together? When reading the burning instructions I believe it stated that the CDrom needed to support as certain mode and that cheap burners don't support that mode. I'm not really sure what "cheap" means, does anyone know what burners do not support the mode mentioned? |
|
From: <edd...@wa...> - 2002-03-20 10:13:18
|
Dave Kaupp wrote: [snip] > I've killed about 8 cd's and had to quit when I ran out. :) I bought a tower of 100 no-brand no-box el-cheapo CDs just to prevent this from happening when I started playing with DC CDs... :) > I used an IPBIN file from I think fivemouse.com and one from DCquake. > Does the IPBIN and firstboot file have to be created together? Yes, they are paired. The IP.BIN file does not only contain data about the software, it also contains the boot code, which initialises the DC. For example, you can't use an IP.BIN file from a game (using WinCE or not) to put in a LinuxDC CD. The code contained is just not the same. > When reading the burning instructions I believe it stated that the > CDrom > needed to support as certain mode and that cheap burners don't support > that mode. I'm not really sure what "cheap" means, does anyone know > what > burners do not support the mode mentioned? No clue... I've got a Yamaha CRW2100S, and before that I had a Yamaha 4416S, and both did/are doing the job perfectly. I can't stress enough the fact that due to the somehow weird (as in nonstandard) nature of those CDs, I never managed to get one correct under Windows, regardless of the soft I was using. Switch to Linux, and try again! Good luck. :) /Dantes |
|
From: M. R. B. <mr...@0x...> - 2002-03-20 11:38:26
|
* edd...@wa... <edd...@wa...> on Wed, Mar 20, 2002: > > I used an IPBIN file from I think fivemouse.com and one from DCquake.= =20 > > Does the IPBIN and firstboot file have to be created together? >=20 > Yes, they are paired. The IP.BIN file does not only contain data about=20 > the software, it also contains the boot code, which initialises the DC.= =20 > For example, you can't use an IP.BIN file from a game (using WinCE or=20 > not) to put in a LinuxDC CD. The code contained is just not the same. >=20 Yes you can. What do you think the distributed IP.BIN files contain? They contain standard Sega boot code - used by all Dreamcast software. The only dependancy between IP.BIN and 1ST_READ.BIN (or whatever you decide to call it) is the boot filename - it must name an existing file. It doesn= 't matter what you call it as long as it exists. See http://mc.pp.se/dc/ip.bin.html and http://mc.pp.se/dc/ip0000.bin.html for further clarification (you can also get an utility from this site to create custom IP.BIN files). >=20 > No clue... > I've got a Yamaha CRW2100S, and before that I had a Yamaha 4416S, and=20 > both did/are doing the job perfectly. > I can't stress enough the fact that due to the somehow weird (as in=20 > nonstandard) nature of those CDs, I never managed to get one correct=20 > under Windows, regardless of the soft I was using. Switch to Linux, and= =20 > try again! >=20 Um, nonstandard? DC bootable CDRs are composed of 1 or more Red Book CDDA audio tracks and 1 Yellow Book CD-XA track. How is this nonstandard? Your "enhanced" Doobie Brothers CD is in the same format. Older and crippled CD burners (i.e. Sony) don't support CD-XA in hardware, but any modern burner should. M. R. |
|
From: <edd...@wa...> - 2002-03-20 14:20:16
|
M. R. Brown wrote: [snip] > Yes you can. What do you think the distributed IP.BIN files contain? They > contain standard Sega boot code - used by all Dreamcast software. > > The only dependancy between IP.BIN and 1ST_READ.BIN (or whatever you decide > to call it) is the boot filename - it must name an existing file. It doesn't > matter what you call it as long as it exists. > > See http://mc.pp.se/dc/ip.bin.html and http://mc.pp.se/dc/ip0000.bin.html > for further clarification (you can also get an utility from this site to > create custom IP.BIN files). And what do you call the areas "bootstrap 1" and "bootstrap 2"? Standard boot code? No way! As MC says: "...this code can be modified. The default implementation sets up a few hardware registers and then transfers control to Bootstrap 2. ... Like Bootstrap 1, it can be modified. The default implementation sets up the CPU stack, the VBR, disables the cache, and transfers control to the 1ST_READ.BIN." As far as I can understand, there is a *default* implementation, not a *standard* one. I believe (from my own experiments) that games using different APIs (as in Sega opposed to WinCE) use different IP.BIN, but that should not be taken as proved. > Um, nonstandard? DC bootable CDRs are composed of 1 or more Red Book CDDA > audio tracks and 1 Yellow Book CD-XA track. How is this nonstandard? Your > "enhanced" Doobie Brothers CD is in the same format. Older and crippled CD > burners (i.e. Sony) don't support CD-XA in hardware, but any modern burner > should. > > M. R. > Having a boot sector in the beginning of the second track, and not of the CD, is not a common thing. Therefore, most CD authoring software don't do it correctly, which leads to weird manipulations. We're not talking odd hardware problems, we're talking general use of software. If it was so straightforward, it would'nt be so long and complicated to burn such a CD. Moreover, do you really believe that Sega would sell a console with no media protection? As advertised in one of their presentations, this implementation provides some sort of protection for the non-literate people, unable with standard software (at the time) to do a perfect copy. Regards /Dantes |
|
From: M. R. B. <mr...@0x...> - 2002-03-20 15:36:48
|
* edd...@wa... <edd...@wa...> on Wed, Mar 20, 2002: >=20 > And what do you call the areas "bootstrap 1" and "bootstrap 2"? Standard= =20 > boot code? No way! As MC says: > "...this code can be modified. The default implementation sets up a few= =20 > hardware registers and then transfers control to Bootstrap 2. ... Like=20 > Bootstrap 1, it can be modified. The default implementation sets up the= =20 > CPU stack, the VBR, disables the cache, and transfers control to the=20 > 1ST_READ.BIN." >=20 I never said it was standard or that the bootstrap code couldn't be modified. But what does the above have to do with the original discussion about pairing IP.BIN and 1ST_READ.BIN? > As far as I can understand, there is a *default* implementation, not a=20 > *standard* one. I believe (from my own experiments) that games using=20 > different APIs (as in Sega opposed to WinCE) use different IP.BIN, but=20 > that should not be taken as proved. >=20 Right, because you're wrong. WinCE games use the same bootstraps as non-WinCE games. There is a replacement IP.BIN on www.boob.co.uk that replaces the Sega bootstraps with non-Sega (OSS) code, but since the license screen can't be removed it's pretty much moot (unless it does something spectacular that the Sega bootstraps don't). >=20 > Having a boot sector in the beginning of the second track, and not of=20 > the CD, is not a common thing. Therefore, most CD authoring software=20 > don't do it correctly, which leads to weird manipulations. We're not=20 > talking odd hardware problems, we're talking general use of software. If= =20 > it was so straightforward, it would'nt be so long and complicated to=20 > burn such a CD. >=20 Any CD authoring software worth its salt doesn't care what tracks you burn to a CD, or what order you burn them in. You burn track 1 as audio, and leave the session open. You burn track 2 as mode 2 form 1 (CD-XA) and close the session. What software is unable to do that? The boot sector is irrelevant as it's inserted by a 3rd-party program (at least under Windows sans Cygwin it is, under Linux you can use cat and dd). The boot sector is embedded in the first 16 sectors of the CD image, and no CD authoring software that I'm aware of cares about or otherwise utilizes t= his data. Furthermore, there have been countless tutorials, guides, and scripts that show you how to generate valid DC CD boot images. Even if you are inept enough not to be able to follow those, do you mean to tell me that you can't burn the countless homebrew demos and games that are already provided in a burnable image? > Moreover, do you really believe that Sega would sell a console with no=20 > media protection? As advertised in one of their presentations, this=20 > implementation provides some sort of protection for the non-literate=20 > people, unable with standard software (at the time) to do a perfect copy. >=20 Windows CD authoring programs were designed for non-literate people, as are the guides that demonstrate creating a bootable CD. The only protection afforded by the GD-ROM media was that it was proprietary, and once that limitation was overcome there were no other protections. Sega did a presentation on how hard it was to pirate via CDRs? Or were you referring to the GD-ROM format? M. R. |
|
From: <edd...@wa...> - 2002-03-20 16:05:00
|
M. R. Brown wrote: [snip] > I never said it was standard or that the bootstrap code couldn't be > modified. But what does the above have to do with the original discussion > about pairing IP.BIN and 1ST_READ.BIN? The code contained in 1ST_READ.BIN is dependant on the system state, as initialised by IP.BIN. That's why they're tied. As long as the 1ST_READ.BIN only needs the standard stuff, it's fine. But you can't say they are fully independant for this reason. > Right, because you're wrong. WinCE games use the same bootstraps as > non-WinCE games. There is a replacement IP.BIN on www.boob.co.uk that > replaces the Sega bootstraps with non-Sega (OSS) code, but since the > license screen can't be removed it's pretty much moot (unless it does > something spectacular that the Sega bootstraps don't). Fine. That's something I didn't dig, just a mere thought. > Any CD authoring software worth its salt doesn't care what tracks you burn > to a CD, or what order you burn them in. You burn track 1 as audio, and > leave the session open. You burn track 2 as mode 2 form 1 (CD-XA) and close > the session. What software is unable to do that? > > The boot sector is irrelevant as it's inserted by a 3rd-party program (at > least under Windows sans Cygwin it is, under Linux you can use cat and dd). > The boot sector is embedded in the first 16 sectors of the CD image, and no > CD authoring software that I'm aware of cares about or otherwise utilizes this > data. > > Furthermore, there have been countless tutorials, guides, and scripts that > show you how to generate valid DC CD boot images. Even if you are inept > enough not to be able to follow those, do you mean to tell me that you > can't burn the countless homebrew demos and games that are already provided > in a burnable image? You're interpreting what I said (or maybe it's my english). I did NOT say that is was not possible, but that is was not straightforward. Audio + CD-XA with bootstrap code is not a *common* CD format, and those wizards thingies under Windows don't allow you to do so. You need to follow a procedure to obtain the correct CD. That's it. If you increase the number of steps, you increase the possibilities of combinations between those steps, and (probably by a much larger factor :) the number of SCREWUPBIGTIME (c) results. That is the weakness of those procedures. The burnable images have nothing to do with it, they're already made. Just dd'ing a CD under Linux gives you a correct image to burn. This is not a very complex task. > Windows CD authoring programs were designed for non-literate people, as are > the guides that demonstrate creating a bootable CD. The only protection > afforded by the GD-ROM media was that it was proprietary, and once that > limitation was overcome there were no other protections. Sega did a > presentation on how hard it was to pirate via CDRs? Or were you referring > to the GD-ROM format? > > M. R. > Well spotted, my mistake. That was about the GD-ROM format. OK, I got this one wrong. :) /Dantes |
|
From: M. R. B. <mr...@0x...> - 2002-03-20 16:22:30
|
* edd...@wa... <edd...@wa...> on Wed, Mar 20, 2002: >=20 > The code contained in 1ST_READ.BIN is dependant on the system state, as= =20 > initialised by IP.BIN. That's why they're tied. As long as the=20 > 1ST_READ.BIN only needs the standard stuff, it's fine. But you can't say= =20 > they are fully independant for this reason. >=20 Sorry, I still can't accept this. Homebrew software and Linux doesn't care about the state of the machine since they reinitialize it anyway. VBR, cache, etc. is either setup implicitly (crt0.s), explicitly (newos, kos, or linux), or ignored. Even Sega software reinitializes the hardware past what the IP.BIN bootstrap provides, and WinCE definitely goes and does its own thing (trust me, I've seen the code). The DC system BIOS and boot block do= es more meaningful hardware initialization than anything the IP.BIN bootstrap could hope to accomplish. Case-in-point: the original Serial Slave and gdbstubs port were available as IP.BIN bootstrap replacements. They did not have any IP.BIN bootstrap routines to rely on, since they replaced them :P. Also, since everyone uses the Sega standard IP.BIN, including games, incompatibility is a non-issue. There is no explicit connection (other than the boot filename field in the IP.BIN header) between IP.BIN and 1ST_READ.BIN. They are fully independent of one another. M. R. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X