Hey everyone Just got my TOOL up and running again, I attempted to run a disc off the disc drive and now I'm wondering if I'm doing something wrong or am I simply missing the sony sdk??? I hope I'm just noobing it and the answer is simple. Thanks guys!
Well, you are, in fact, kinda "noobing it", but everyone has to start somewhere... First, rtfm ("find --help" or better yet "man find"), then try again with "find / -name dsedb" (probably gonna take a while - It's searching through the whole disk since I have no idea where dsedb is supposed to be). Oh and most of the time you seem to keep omitting the space that goes between the command and its arguments, it's supposed to be "cd<space>/usr/bin", "find<space>./sdk" etc.
You guys rock! I was able to find that my TOOL is set up to be used as a target box............ the PS2 SDK is NOT loaded in the directory where it should be in, thus the TOOL is like,"WTH are you talking about man?". Now I'm back at the predicament I was trying to avoid, setting up a host box. I have the PS2 skd files loaded on my Macpro but as I recall from my previous attempt at installing the proper Linux with the proper kernel via Parallels, Linux hates my Xeon machine. Well, Thanks everyone for your VERY valuable knowledge contributions!
Of my TOOLs, all contain the debugger and target-side utilities (mrp, dsnetm and stuff with extremely low version numbers), but I have never seen SDK files like the headers, compilers or example code loaded onto a TOOL. Given the lack of disc space, RAM and CPU speed, I also think it wouldn't be worthwhile to develop on the TOOL itself... As for your Mac, I think I read somewhere that some Linux distros have trouble with the installed Xeons. You may want to search the Apple newsgroups for this, someone might have found the right combination of boot parameters to get it working. By the way, what do you mean by "proper kernel" for the development system (Linux VM)? You don't need to use the same ancient kernel version that is installed on the TOOL. The SDK only includes user-level code, no kernel modules, so it should basically run on any current Linux.
OMG Silverbull, you have just taken a big load off my chest, I thought I had to run a specific kernel version of Linux to communicate with the TOOL, point blank, the point of this TOOL is to run masterdiscs and games at a vintage museum, running dsedb for game boot up is it's purpose. No real programming or advanced anything is planned in the near future, it's already a time vampire as is.
You're welcome ;-). Does your TOOL's HDD contain DSEDB at all? All I've seen so far do, so if all you want is to run games, you don't need a separate development PC/VM. Just run DSEDB on the TOOL and start the game from there. You might also want to use the simpler command "dsreset 2 100" (at the normal Linux/Bash command prompt) instead of the debugger. If you are already running DSEDB, the command is "reset 2 100". Please note, though, that these machines are ancient and their HDDs (or, more likely: their lasers) may fail. I understand that running games on a TOOL has a certain coolness factor, but in the interest of conserving the laser, I strongly recommend to use a normal PS2 (believe me: exchanging a TOOL's laser is a pain).
