Re: ... I know what you mean - when mine arrived it was in CPU mode tried to boot a game was like WTF :smt017 A few days later when my SCSI equipment arrived I had a play with the tools and discovered the option to boot in OS mode in DA Check :smt023 Then later discovered in OS mode with codescape you can manually load a debug binary into the memory (I used the Memory Card Utility). The other cool thing about CodeScape is when you use the Screencapture utility, after it takes the .bmp the Dev Box locks up, but wiht codescape you can 'unpause' the CPU and carry on as if nothing ever happened :smt033 *Sigh* when Dev Box goes I'm gonna miss the ScreenCapture Utility :smt022 it is very handy for games reviewing, archiving glitches in retail games and GD-R and making pics for website Much better than a TV capture card
Re: ... Hello? did I miss something? or are you talking about eventually, in the future when the electronics burn out?
.... You do not need codescape to restore the devbox's running state... DCcapture utility has two capturing modes...the second one makes the devbox run again if you press the "play" button.The other button that actually halts the devbox gives you the option for better screenshots as in many situations artifacts appear.... And yeah,it rules...was playing rez and cpaturing screenshots to stdy the various visual effects
Re: .... I know but the documentation is full of shazbot 99% of the time the play button never actually restored it!!! I have only witnessed it continue play maybe once!!! Hence I resorted to CodeScape :smt023
It actually states somewhere in the files if I remember correctly that play does not allways restore as the progam is still beta or whatever. i guess probability was against me.Oddly enough though CodeScape ALLWAYS restored it - surely the capture could use used the same command -_- or been equaly reliable. I only had R10 though possibly the program was fixed in a later SDK.