|
Post by Gamesoul Master on Aug 22, 2006 11:11:16 GMT -5
I'd actually strongly prefer that you leave the DTLH BIOS options. At the very least, leave the DTL-H3000 and DTL-H3200.
SCPH-2000 is a prototype mouse/keyboard adapter, SCPH-5500 *is* on the list (maybe you meant SCPH-5000?), and SCPH-103 (which I've not heard of) probably came out after that list's last update (which was July 13, 2001). I'd like to add that... it's been said by a lot of sites that SCPH-2000 is a developer model of the Playstation, so maybe the site just tacked it on to the end until they could confirm/disprove it (you notice it said "Nothing else known").
DTL-3000 was mentioned like that because the model is apparently known as either DTL-3000 or DTL-H3000, and maybe there is only a difference of color between these two, which could've very well led to people distinguishing the two colors by the addition or removal of the "H".
Here are the BIOS I recommend for each region based on availability, age, and compatibility:
- Japan: SCPH1000 or SCPH3000 - EU: DTLH3002 or SCPH1002 - US: DTLH3000 or SCPH1001
As a note, I recommend (until/unless I discover otherwise) DTLH3000 as the most compatible BIOS for any region. (patrickp, if you could test this theory on PAL games, I'd greatly appreciate it).
|
|
|
Post by patrickp on Aug 22, 2006 15:07:26 GMT -5
Will do, GM. I'd like to add SCPH5552 to the list; it's a nice one for PAL games and, although I think SCPH7502 is rubbish, I think that should be included, too, since it's by far the most widely available, and the one people are most likely to have.
And particularly, I think DTLH3002 is the guv'nor PAL BIOS, Ultima. Should not be omitted!
|
|
|
Post by Gamesoul Master on Aug 25, 2006 19:50:44 GMT -5
I'd like to say (since this thread may soon start to become dead as the frontend achieves perfection) that maybe this thread should be stickied. It's a very highly useful frontend to accompany the simple out-of-the-box theme behind pSX. I may even be so bold as to say that maybe a note could be added to the readme of pSX, or the home site, giving a link to this thread for anybody who wants a simple way to manipulate the command-line features of pSX.
|
|
|
Post by patrickp on Aug 25, 2006 20:27:20 GMT -5
Seconded!
|
|
|
Post by Ultima on Aug 25, 2006 22:04:33 GMT -5
Hm, I guess I could do that, but where should I make a sticky regarding the frontend? This thread would be too confusing for some people to follow (due to a lot of development talk), so I hesitate to stickify it. Should it be an announcement? Just posted in the Important Information subforum? Stickifying in the Help and Support forum seems too... specific a forum, as I don't see it being a tool limited to Help and Support. Suggestions? And about the BIOS stuff... Maybe I can modify it so that you can select based on region, and thus list all BIOS versions without fear of hitting the 30-item limit, but it'd be separated and more difficult to find specific BIOS versions that way if you're not sure what region you want to use (for example), not to mention it'd be a bit more annoying just in general to code in. So if anything, I'd rather keep the current system (lol refusing my own suggestion), but even still, I'm not sure what BIOS version I should leave out =T
|
|
|
Post by Gamesoul Master on Aug 25, 2006 22:18:28 GMT -5
My quick opinion to the BIOS question... I'd say if you need to leave any out, leave out the least common ones (except for the DTLH ones, of course). With that, place an emphasis on keeping the older BIOS if it comes down to it.
As for the rest... I'd say sticky this thread, and add a locked announcement with a link to download the frontend. In the announcement, describe the frontend and give any other notes of relevance to people wanting to download it, in addition to a link to this thread if they want to read "the thread that started it all", as I like to put it. But I strongly suggest stickying this thread, as it is also here for suggestions on adding/improving features and also any bug reports. Not to mention this isn't like a compatibility report (which eventually fade, but get added to the list), because even if it starts to fall down the list of threads, there will always be people using the frontend with that number of people increasing, since us (your biggest/original supporters on this frontend) and yourself keep a link to it in our signatures. In all, this thread is very important for anything relating to the frontend, and so should be stickied for everybody to easily see and access when needed.
|
|
|
Post by Ultima on Aug 25, 2006 23:15:17 GMT -5
Stickified, will make an announcement later
|
|
|
Post by TheCloudOfSmoke on Aug 26, 2006 7:41:46 GMT -5
I think that you should make a new clean thread and sticky it with all of the past versions and the current version on the first post as this thread has all of the versions randomly scattered throughout different posts. When you make a new version to accompany a new release of pSX, you can just edit the first post.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 26, 2006 10:36:38 GMT -5
I agree with CloudOfSmoke. A clean and locked sticky with changelogs, link to this thread, and link/s to latest (who really needs the older versions?) version of the frontend. And all other relevant information.
|
|
|
Post by Gamesoul Master on Aug 26, 2006 12:15:30 GMT -5
Well, that would pretty much be the same as a locked announcement that I had suggested. I only figured making it an announcement because Ultima said he wasn't sure that it fit into any one thread. And... I think this frontend should get as much viewing as possible. It really is a great frontend that I think everybody should try, and an announcement would really help for many people to find it, as it seems while most people can't see important stickied threads so well, they see announcements a lot better.
But ultimately, the choice is up to Ultima. Either my suggestion or CloudofSmoke's suggestion would be good.
|
|
|
Post by Ultima on Aug 26, 2006 14:05:10 GMT -5
Heh TheCloudOfSmoke's reasoning was the exact same reasoning I had... I guess I'll change back to that then I'm still not sure if I want to post in the News and Announcements forum, though, as this is not an official project by pSX Author, and if I post this there, then other third-party projects would have to be announced there as well (to be fair). Edit: I just figured out a way to hide the log window when running pSX, which would satisfy a lot of requests =o I wonder if I should include this feature, though, as not displaying the log window would mean a lot of people miss out on some important information =T Edit: ROFL how stupid of me... I just realized that there isn't a 30-item limit on the combobox... it's just that I didn't have it show a vertical scrollbar... w00t, pSX Frontend v1.07 under way with the 43-version BIOS list in its full glory and the hide log window option included.
|
|
|
Post by Gamesoul Master on Aug 26, 2006 17:58:46 GMT -5
Meh... the funny thing is that my frontend *accidentally* closes the DOS console window. Well, I might have actually fixed that with my last release, but it was a while ago and I can't remember. Or it was my java-version that did that. It didn't cause any problems, but it was weird to not see it open. I think I actually commented somewhere in here about that happening, and about how that would probably make some people happy... As for adding the hide option, don't forget to add a little warning to the readme saying that the DOS console isn't needed for normal gameplay, but any filed bug reports need to include anything the DOS console might say (meh... or however you wanna phrase it... my wording needs work I think). Anyway... anybody try the other frontend that random person released? I think I'll check it out, just in case it has something that neither of ours has (so we can add the feature, and give credit of course... XD). Edit: Tried the program. Quite interesting... can't decipher the language from the program itself or the code, though. The syntax is lost on me. Anyway... the only idea it yielded was the one Ultima already commented on... the option to mount the image using Daemon Tools. Maybe you could try it out, Ultima... possibly play around with the concept a little and see if you like it. It would certainly contribute to completeness, if nothing else. You could possibly even add support later on for *other* virtual drive programs. Although I'm not sure if you'd think the trouble would be worth it (for myself, it would be one of the last features I'd implement, only after implementing and perfecting everything else I could think of).
|
|
|
Post by Ultima on Aug 26, 2006 18:26:06 GMT -5
Hm, I don't think I'm going to bother with DT. It's a cool idea and all, but if someone really needs to, it's not that hard to mount an image, and it's a LOT of work for only marginal benefit, especially if I ever were to come around to support a bunch of different drive emulators.
|
|
|
Post by patrickp on Aug 26, 2006 18:34:24 GMT -5
I don't know, does it actually get Daemon tools to mount the image, or does it just use an already mounted image? If the latter, then there's no real difference between that and CD drive, really...
Certainly, anyone who plays the emulator full screen (as I do) doesn't give two hoots about the DOS window, except that it's there if needed, and I have no problem with it even in windowed mode. But a number of people _have_ posted saying they don't like it, so I guess...
|
|
|
Post by Gamesoul Master on Aug 26, 2006 18:35:26 GMT -5
Ultima: Yeah, that's what I was pretty much thinking. Besides, there really isn't much use for it, as there really shouldn't be any problems with people loading images that wouldn't occur if mounted first (at least, not nearly enough need to go through all the trouble). So... will we get to test drive v1.07 tonight, you think? Edit: patrickp: It actually mounts the image. You just have to make sure to set the proper drive to read it from. Mounting the image and running the game are done as two separately different things. I told it to mount an image (which is "M:" for me), and then didn't tell the frontend which drive it was (defaulted to "F:"), and I got a whole bunch of bad errors in the DOS console, not to mention the game obviously didn't start.
|
|