Ok so I got to work today and made some real progress. Decided I'd start from scratch and just format the computer and fresh install windows 98se. So after windows installed, I went straight to putting the psx dev files in the right directory, gave myself more environment space and ran the batch file, no errors. After the restart I got a video signal from the dtl-h2500 for the first time ever. Was quite an accomplishment. Then I found the psyq debugging programs in the \pssn\bin dirrectory and using this, I was able to change the video out from the h2500 from ntsc to pal, then back to ntsc again. Also ran SN Systems Diagnostics and all checked out ok. So This confirmed to me that the dtl-h2500 is communicating correctly with the computer and software. There are still some problems. Software-wise, the dtl-h2500 still shows up as a question mark in device manager. However, windows no longer prompts me to search for the correct drivers on startup, so pretty weird. Also, when I tried to run the "shuttle" sample, I only got an "aborted" message. If I keep going, trying to get the sample compiled, I get a "cannot find how to make" error Hardware problems, Ive mentioned this before, But I still need a dtl-h2510 cd-rom playstation drive for the board that I'm using. I'd really like to have this running 100%, and have it complete, and this is the biggest piece I'm missing. I should still be able to compile and test samples with out the drive, right? My controller question also was never answered, Which is: I have the controller port/memory card ports from a retail playstation console, would I be able to directly wire this to the dtl-h2500? I ask because the controller ports on the dtl-h2500 is 10 pins, and the controller/memory card ports are also 10 pins. I dont have the controller with serial connection that goes to these boards, but even if I did, I would still want to do what I just asked because then I could use whatever retail controllers, as well as memory cards.
Here are some screenshots of what I was talking about before: This one shows the SN Systems diagnostics pass I was talking about, It even resets the dtl-h2500 as its going. And this one shows the problem I'm getting while trying to run the sample program on the dtl-h2500.
Hmm... Thats weird. Is there a CR2032 battery on the board? Maybe it can not set something because it is dead. I dunno. Thats just a no0b's guess. lol. Check the dip switches?????? Wish I had that SDK kit. Your lucky
Looks like your compiler can't find the libraries headers... Therefore, you seem have path issues. (considering that you have the files it's asking for) I cannot help you any further than this due to absolute lack of specific knowledge related to the devkit you're trying to setup.
Well I might put some up on ebay since I have so many. only once I know which ones are 100% working though. Yeah It has that cmos battery you mentioned, but I recently replaced it with a brand new one so I dont think that could have anything to do with the software issues. Are you referring to sys/types.h, libetc.h, libgte.h, libgpu.h, and libgs.h? Could these be in the wrong directory? If I find them, where should I put them? This seems like it should be easy to fix... Once I know where everything should be.:banghead:
Please upload your autoexec.bat / config sys. Im pretty sure the compiler path is wrong. On your screenshot i see you try to use the PSSN compiler. Try using the compiler in the PS Folder from sdk. Can you run h25bios with your h2500? When the h25bios is execute correctly, your h2500 is OK. Otherwise you maybe has some IRQ problems. I have many problems using AGP graphic cards with the h2500. But first step is to get your compiler running. I can post you an running config for the h2500. Also the windows driver ;-). Yes, you just use the "run" to execute compiled code. But for using "run" you musst be sure h25bios is running! Do you have the AV cable? I think so. When you like to build up something, i can have an look on the pinout. Maybe worth to try it regards Chris
Formatted (again) in an attempt to get usb working (pain in the ass on old hardware/software) Unfortunately this time things didnt go so smooth. :gravedigging: I can no longer get the dtl-h2500 to boot up at the same time as the machine, instead now I have to execute h25bios. Also, the diagnosics now says there is no dtl-h2500. On the other hand, I flashed the dtl-h2500 and now theres numbers on the screen on top of the colorful vertical lines, as seen here: http://www.assemblergames.com/forums/showthread.php?t=17766 before it was just the colorful vertical bars. I dont remember what I did last time to get the dtl-h2500 working the way it did, so If someone can help me get the driver installed correctly, thanks.
Currently, I can use h25bios and when I execute it, the dtl-h2500 board turns on and sends a signal. I made my own cable and it works great. Below is an attachment of my autoexec.bat, I changed the filetype, just change it back to .bat when you get it. Here you see the dtl-h2500 turned on (with the video cable I made) with the colorful bars and the numbers I was talking about Here's h25bios executed and heres the system info, last time there was a question mark but it still said playstation pci, not it just says pci, so you know its not installed correctly...
Please be careful here, as you can easily shoot yourself in the foot by installing arbitrary drivers for this card. I think Jackhead (please correct me if I'm wrong here) needed to re-install his system multiple times because he always installed the driver and then wondered why nothing worked... You can operate the card in two modes: With the PSYQ utilities (DOS box only) With the DECI utilities (Win/GUI mode only) These are mutually exclusive; you cannot use both the command-line PSYQ utilities (like those for the DTL-H2000) and the GUI utilities (SNSys' tools) at the same time, as both require different flash ROMs on the card. Look into the READMEs in the firmware folders (the "public" collection of PSYQ stuff has at least three different versions of the firmware), there should be a statement whether the files are for the "DECI" or the "PSYQ" mode. Depending on what you want to do, you use either H25BIOS for PSYQ or the VXD for DECI applications. Do not install the VXD if you are going to use H25BIOS, and do not start H25BIOS if you have installed the VXD. In PSYQ mode with H25BIOS, the yellow exclamation mark in device manager is perfectly fine. I assume the GUI diagnostics program won't recognize the card in this configuration, although the command line tools should work fine; I have never tested this on my setup, though, as I never used the GUI stuff.
Ok, So I've already shot myself in the foot... I managed to start a program through the command line, but I'd prefer sn systems, so it seems like I'll have to reformat again tomorrow. I'll get it right. I want to use sn systems because then I can use a newer flash, the one that shows the numbers rather than just the colorful vertical lines.
I think you don't need to reformat in this case. H25BIOS is a memory-resident program (TSR), and leaves no permanent traces in Windows. Just reboot Windows to get rid of it. You should then be able to re-flash and install everything that is missing (including the VXD). I recommend keeping a "cheat sheet" of the various flash versions you try and whether H25BIOS and/or the VXD and DECI applications work with them. H25BIOS is not compatible with all of the different firmware versions, and may freeze Windows completely if you load it with the wrong firmware installed. The VXD might act the same way... I am quite sure you need the DECI firmware for all applications from SNSystem, but as I wrote last time, I never tried this setup :shrug:. Good luck!
I've never used the original dev equipment but you should be able to use the SDK from the archive which is floating on the net, just saying.
Exactly this archive is the problem, as it has been "compiled" (or, better: botched) from different versions of the SDK with different path layouts, installation instructions and so on. Even though all files are included, it still takes some experimentation to put them together and get a working PS1 dev setup.
Yeah I figured thats what happened. I tried looking for the discs, but no luck, Anyway, I ran the "ball.exe" program and now know which boards are working and which are not. Does anyone know if I can use the controllers with ball.exe? This would be the perfect opportunity to try experimenting with the controllers, wire some up with serial connections, or hardwire the ps1 controller ports to the boards. All I see is a little ball bouncing around on ball.exe.
