Was there any systems that the sdk was made for dos only? I would like to work on a project, but I need it so be in dos. Thanks
Basically all of the old ones used DOS. Probably the last generation of systems that you could realistically develop for entirely in DOS would be the Saturn and the original Playstation.
Well if I program for ps1, what version of the sdk should I use? Also any idea about an ide or tim editor for dos?
With a bit of fiddling, you could persuade the IDE used by Borland C to support other toolchains - I used to develop code for the 8051 in it. Graphics stuff is a bit harder - there are DOS based converters for TIM format, and I guess you could use something like PC paintbrush or the MS-DOS version of Deluxe paint to create the images and then convert them. There are also converters from for various 3D formats. I guess you could use one of the old versions of 3D Studio - I think R4 was the last DOS based version before they released the 3D Studio Max on NT. Sorry I can't be more precise, but it was a very long time since I used any of these DOS based tools...
By the way if you compile them with DJGPP, the tools from PSXSDK should also work. With some work you can also get the psxsdk toolchain up and going on dos. EDIT: I've just compiled bmp2tim, mkpsxiso and wav2vag from the PSXSDK tools for DOS with a djgpp cross-compiler. This is the zip archive.
Thanks for the download. The whole reason I want to do this with dos, is to make use of my raspberry pi for game dev. Looks like it will be quite the challenge[FONT=arial, sans-serif].[/FONT]
So you want to use development tools under DOSBox running on the Raspberry Pi? While running the tools under DOSBox is the easiest way and you can use the original sdk that way, if you feel technically versed enough and your Raspberry Pi runs Linux, you could compile a PSXSDK toolchain for it, it will be much faster because it's native. toolchain.txt in the PSXSDK source distribution explains how to build a toolchain for use with it - known issue: add --enable-languages=c to the GCC configure command line recommended by the text document.
My Raspberry Pi does run Linux (desbian), The only thing is, I'm not well versed in Linux. Most of my life has been spent using dos and windows. I guess I need to start looking into the file structure of Linux more. Everything just seems to be more complicated than in needs to be.
