New PS2 Tool owner, have some questions...

SilverBull, you missed a few rpm packages like gstool and powctrl.

 

Ah, thanks. Did you ever see these files in non-installed/RPM form? Maybe even as a source RPM? :love2:

 

Nothing except an old version of gstool on the 2001 TechRef disc iirc.
No SRPM anywhere...

 

I had expected that, would have been too nice... :banghead:

I'm currently thinking to "reconstruct" at least the normal (binary) RPMs from the installed files, which would allow us to reinstall Linux on the TOOL (just in case no appropriate HDD dump is available). I've seen some patch files (used to insert the calls to toolled into the regular boot process), so I assume this would be possible for at least some of the RPMs you mentioned. Did you ever package files into own RPMs?

Did you notice the GPL tag of the powctrl-ps2dev RPM? If it is really GPL, Sony would have had to distribute the source code to at least this package. I think I have seen a reference to the official compiler's source (based on gcc) somewhere (maybe a newsgroup posting in the SDK/TechRef, referring to the member area of ps2pro.com?), but I'm sure I've never seen the source of the vmlinuz-2.0.36-ps2dev "kernel for ps2dev (special power control daemon)".

 

time to jump to another matter once again

apologies for derailing but i really didn't feel like doing another thread with about the same name, so here we go:

1) does the TOOL have capabilities to capture video and/or screenshots ?
2) if above is yes, what would i need to accomplish either or both ?

i have some stuff i'd need to take shots of about but i really don't feel like using PcSX-2 and fraps since my PC runs ps2 crappy enough even without the extra load

edit: ..gotta lern2type

 

There is no native video capture function, but a TV grabber card hooked up to the TOOL's multi A/V out should work. Some graphics cards also have a composite or s-video in, as do some on-board graphics chips.

On the other hand, the TOOL can take screenshots directly from the PS2 video RAM, but it is hard to use and buggy as hell: requires some rather obscure parameters, doesn't always work and can completely screw up some games :banghead:.

Unclejun has a program named VRAMSNAP to perform screenshots, and I'm sure he'll jump in soon. If you want to screw around with the TOOL in the meantime, read on, as VRAMSNAP is simply a nice GUI+conversion utility for a special debugger command (RDIMG). There is also an (innocent-looking :evil DSEDB command to perform the same operation, albeit at a much lower level of abstraction: STOREIMAGE. If you want to see it in action, you can try to get a snapshot of the network information screen:

• Make sure the network information screen is displayed. Shutdown DSEDB if it is running, then run /usr/local/sony/bin/devtool-opening on the TOOL itself (this script is not installed as part of the SDK). Once it appears on the TV, do something like this (either on the TOOL or on the development PC with the SDK installed):
• dsedb -nr (start DSEDB without target reset)
• storeimage ~/test.image.bin 0 8 0 0 0 200 800

When trying STOREIMAGE during a game, be sure the game is stopped (BREAK).

This command takes some seconds, but it should eventually produce a 4MB raw dump of the VRAM under the name test.image.bin in your home directory; either that, or it simply displays an error message like *** Timeout, indicating your game is not ready for taking screenshots yet. If this occurs, I'm affraid there is nothing you can do; you can try issuing some STEP/NEXT commands to get to some outer procedure scope, then try the original STOREIMAGE again. Or CONT and another BREAK at a later time, hoping it stops in another more suitable context.

The parameters of STOREIMAGE after the file name almost directly refer to the corresponding parameters of the SDK function sceGsSetDefStoreImage, which in turn relies directly on the internal organization of the PS2's VRAM. I found these exceptionally hard to understand when I first read about this stuff. Let me know if you want to know more, I'll then try to write a short summary.

Unfortunately, I don't know of any program capable of converting a raw VRAM dump file into something more useful (like a standard bitmap); even VRAMDUMP needs a live connection to a TOOL to perform its work.

When I first wanted to take screenshots, I didn't now about VRAMSNAP, so I ended up writing my own dumper :banghead:... on top of my own DECI2 stack :evil:. This program uses the same parameters as STOREIMAGE does, but it displays a real-time preview of the captured image, so I found it quite handy when trying to understand VRAM organization...

In contrast, VRAMSNAP only allows to select certain common image resolutions (in addition to the pixel format). Therefore, it is much easier to use, but at the expense of flexibility. For example, if you want to take just the contents of the display area, rather than the whole VRAM, you have to save the whole image first, then remove the irrelevant parts.

Here's an example output:



To get this image using VRAMSNAP, you simply set it to use a Width of 640 pixels, starting at page 0, pixel format PSMCT32 (other settings result in a distorted image, but finding the correct ones is relatively easy). Then, save the image, and cut away everyting outside of the visible area.

In comparison, when using my program, you have to enter all parameters of STOREIMAGE manually, until you get an undistorted picture (in this case, they are: bp=0, bw=A (hex!), x=y=0, w=280, h=200, format=PSMCT32). However, once that's done, you can save the above picture directly.

I've been planning to release this program for some time now, but unfortunately I haven't found the time to prepare it accordingly (it contains a lot more functions to control a TOOL than just the VRAM dumper...). If you want to give it a try anyway, please feel free to send me a PM.

 

i suppose the first thing i'll do is set up the dev PC with an SDK then

that was certainly a bit more than i expected but i suppose a TOOL stays being as complex to use as i heard. (i really got a long way to go )

im not sure about the SDK thing really, i got some stuff (not installed yet) but what apps exactly do i need to install on a devPC in order to be able to control the tool ?

i know Parris sent me a disk with some stuff on it, but the postal service stole it so as of now i might be screwed regarding that.

i'll take a peek on that STOREIMAGE tho in a day or two when i once again assemble the unit

and since im worse than the bad students at "linux for dummies" school
how do i check if DSEDB is running and shut it down ?

 

I'll try to answer to both of you, it might be messed up...
-I did, but it was a long time ago, nowadays I would check http://rpmrebuild.sourceforge.net/, it's probably easier.

-SilverBull answered the questions well.
You probably noticed the S-video connector on the Tool, you want to have a guess of its purpose?
pcsx2 can save screenshots and record videos by itself.

A few pics for you to see:


dsedb has its own prompt, you can't miss it.
You can quit dsedb with the commmand "quit", quite obvious isn't it!

 

so the s-video works for capturing then
distracted me a bit as it says "input" on the back and i obviously want output
so yeah, now i gotta get something to plug it on, i don't think i have any suitable gadgets on the pc

also, here's what currently bothers me the most on the whole tool thing:

i can obviously handle the tool directly from the tool as im doing now. but what do i need to handle it via the dev pc.?

the SDK readme files are all in japanese so im at a total loss with them and got about no idea wtf im doing. it also seems to be linux stuff so i think it's safe to assume i need something extra to run this thing on windows. (cygwin?)

and the other question is the "home folder" (~/test.image.bin)
is this located on the tool itself or does it work via the SDK so that the home folder would be in the dev pc instead ?

I know, another wall of questions
my apologies.

i honestly have no idea where to even start installing the SDK.
my linux usage is pretty much restricted to installing one and using irc/firefox on it.

 

It really is an S-video input, the Tool can capture video, not its own though!
Sorry for keeping your hopes high...

dsedb is only a client, you can run it locally on the Tool or you can run it on your PC and specify the IP of the Tool you want to control.
I sent you a PM.

 

oh well. i suppose it's about time i upgrade this pc to be on par running the emulator for the video capturing purpose

as for the PM, thanks for that, replied weith hopefully sufficient info

on a slightly off-topic now,
as for now i most likely located a suitable "donator" for the TOOL to finally repair the broken drive so the change of plan is now to hold-off putting it together until i receive the spare parts

it's really too much work to disassemble and reassemble it on a daily basis

edit: happy 200 posts to me \o/

 

Well, I've become the proud new owner of a TOOL thanks to daytonausa (I figured it'd be reasonable to continue questions about this system in this thread) - I've gone through the previous threads, and unless I'm missing somehting, I'm in dire need of the SDK- I see version 3.0 mentioned a lot- is this the last build?

I do have a copy of CodeWarrior for PS2 1.5 sitting around on some really old cd's I got back in the day with my XBox XDX CDs... is this of any use, or is this too, outdated as all hell?

Info on how to get the software components I'm missing would be appreciated-
Also, what is the deal with the T14K, it seems in rare supply, and is it really as easy to use as it sounds, allowing simple uploading of disk images mastered with CD/DVD ROM Generator to the system for testing/run?

-dan

 

You don't upload disc images but the files directly to a single partition set as a CD or a DVD.
It's way faster and easier than to burn a new disc each time you want to try something different obviously.
There are more Tools around than T14k boards sadly, because it's a must-have.

 

Ah, makes more sense, so as to save updating an entire disk image in the emulator just to try a single new file...

system is the older 233mhz, 64MB, IBM DTLA-305030 drives (30GB)
DTL-10000H

and either one drive is going or there's a fan that needs MAJOR bearing changes- I'll do a full teardown and cleaning tonight or tomorrow.

If it's the drives, is the system (linux half obviously) picky about the drive used, or can I just dd the old disks to something quieter- alternately, I can always pick up NOS DTLA-305030's dd the data, then swap the old controller boards onto them...

In the end.. gonna need the SDK- only references I've seen to it around are old torrent links that are dead and expired- help?!

 

it's not the HDD's, it's the fans.
as you said that you read some of the other threads, im sure you have noticed the tool constantly being referred as "the noisy beast"

im on my way to replace them all on mine when i get some more time in an attempt to quiet it down a bit.

as for the SDK, i certainly have absolutely no idea about the lastest version of it, myself, i have the one labeled as 3.0

as for replacing the HDD's, there shouldn't be anything special to them aside the data inside obviously. Now, im not 100% sure as usual since im somewhat a newcomer with tools too but i remember hearing that somewhere around here that any 6Gb++ size HDD will do.

on hte matter of the T14k board, im still semi actively looking for one. I didn't believe they were so rare :crying:

 

lol, I agree- they seem to have been pretty aggressively marketed by sony from what I can see...

the noise was actually neither the hdd's nore the fan (directly)
in fact it was one of the ata cables hitting the p2 cpu fan!!! especially finky given the system had never been opened!

anyway- easy fix, bending it out of the way- took the opportunity to clean the insides free of dust, the fans are a little noisy, but FAR from what it was!

no damage to the cables either, so it might have happened in shipping- the decorative base was totally smashed on one corner by UPS ... somehow I think that i'll probably have more trouble finding a good condition base than the T14k, but the system kinda looks better without it... it just doesn't match my TEST now

THe power supply appears to be a stock ATX PSU, I've been thinking of reworking a lot of the components for a more prolonged lifetime- Fans, PSU, HDD's, possibly tracking down a low-power Pentium M PCI-SBC to replace the existing p2 board (even though its unnecessary, making the system more durable in the long run might be a smart idea...

 

afaik there is something on the psu that makes it different from a standard pc one..
ASSEMbler posted something about it somewhere around here..

and yeah, i can feel you with the stand, mine's partially shat too,
even tho i managed to parse it together so that there's nothing visible unlessyou take a close look.
Still annoys me mildly as it's such a beautiful unit and
now it's just complelety shat by the delivery.
My second unit suffered the same fate.

i like how it looks with the stand tho, so i'd rather have an intact one than
keep it without the stand.

as for replacing the cpu and such, not a clue from that one, i do have one of the "old style" cards (RAM destroyed by delivery) with the 233mhz cpu on it but the main unit I run has the PCI815VE card which comes with 128Mb RAM and 566Mhz socket 730 CPU which is relatively easy to replace were it die on me.

Im sure Unclejun and the other resident tool masters in here can fill you in about replacing the CPU on the oldstyle card.

edit: also, as for the joint effort of silverbull and unclejun to get me started on toying with the functions of the tool itself a bit,
i finally decided to boot it up and toy a bit regardless of the fact that i still haven't backed it up

here we go my unit as seen through the VRAM
thanks guys, very, VERY appreciated.

 

I was thinking more of replacing the entire card- it's a stock pci half-length sbc... as long as the build of linux will communicate on the pci bus the same, any normal one should work from what i can tell

 

oh well, i suppose that's an option too
didn't think about replacing the actual card as im going to try and keep mine in it's original condition

would be nice to know about what kind of card did you use and how it worked out if you get around actually replacing it. who knows when that old
hardware died out on me, so having options is never a bad thing.

 

got the system to boot up master discs with no hassle (after doing the reset stuff), booted the opening screen.. seems the system's domain name is midwaygames.internal
Last time the system was logged in directly is Feb21, 2001

anyway...
is there a way to reset to a stock ps2 bios of sorts, or does the system always need a reset even to get going, and even then, as it indicates, need a disc inserted?
pretty awesome so far, gotta go pick up a component to vga adapter or something so I can use this on my main monitor

Should I check for game data on here, and if so, where would it be stored?