Help me please, See Inside

[haronpogi]

I'm not really good in coding and other stuff like that and wish I am so I dont have to ask for help. I have a brigandine.bin and brigandine.cue, i have psx v1.9 and everytime i try to run and do Insert Image. then it asks for .bin/cue and etc. but everytime i do this it wont work, nothing shows up in the psx v1.9 window, just blank black, please someone help me because i really want to play brigandine.
heres my e-mail [e-mail] and this is my Sn if you guyz have AIM. thank you and hope to hear from you guyz

can some tell me what to do exactly with this bec. im trying to make this work for 2 days and trying to firue it out and still wont work.




after i click whichever of those two files, nothing works, just a blank black screen
i read "read me" and try to follow everything but still wont work
I really wanna play this game and pls someone help me

the keys work like when i press enter thres "MUTE" i press tab and i saw this and idk wat this means, and actually i dnt know wat scph101.bin means so please i would b really happy if sum1 help me

[TheCloudOfSmoke]

Since our technical support staff isn't available at the moment, I will make an attempt to help you solve your problem. I don't know about the compatability of this game in pSX because I never even heard of it before but I did notice that you said that you saw a black screen when you tried to play it. Does this happen with all of your games, or just this one? If this happens with all of your games then you might need to install the latest DX from the microsoft website.

www.microsoft.com/downloads/Browse.aspx?displaylang=en&categoryid=2

Quote from the FAQ:

Q. All I see is a blank screen when I try using pSX... help?
A. Make sure you have DirectX 9 installed, and check that your hardware drivers are up-to-date (video card and chipset drivers especially).

EDIT: Just checked smegforbrains compatibility list and it says that the game works but there are "cdda buffer overflow" errors".

[pSX Author]

See my reply in your other thread - you don't have a valid BIOS file.

[Gamesoul Master]

Technical support has arrived! ... ... ... Oh, it seems things were handled without me... -.-;

Anyway, it's starting to look like one of the admins should make an entry to the FAQ for this kind of problem. Like...

Q: As soon as I try starting a game, I get error messages in the DOS console saying "r3000: executed illegal opcode" followed by 8 numbers/letters, and the emulator just stays at a black screen.

A: There is a very good chance that you have an invalid BIOS set. You'll need a valid BIOS set in order for the emulator to start. Also, if you're using an image, it may be a bad dump, or the game might just not be compatible.

Admins... feel free to use my wording, as I know it is too perfect to pass up... ;D

[Ultima]

I don't think it's only starting a game, but rather, starting pSX itself, since pSX attempts to load the BIOS regardless of whether you insert a game *steals FAQ entry from Gamesoul Master*

[patrickp]

I just tried creating an empty file called scph1001.bin and the emulator wouldn't start, just as if there were no BIOS at all. So I guess there must be _something in haronpogi's file that the emulator recognised as a valid BIOS.

haronpogi: it's not a good idea to post your email address on a public forum. You're likely to attract rather a lot of spam this way. Unless this is a 'throwaway' address and you don't care about the spam, it would be a good idea to remove or 'munge' it. Munging is the practice of writing an email address in such a way that a spam bot either doesn't recognise it as such or picks up an address that isn't valid (and you should make sure it isn't - you don't want to lumber someone else with spam). In either case, a human reader should be able to reconstruct the real address from the information given.

A simple example would be the practice of replacing the @ with the word 'at.'

[pSX Author]

Currently there is no check for a valid BIOS in pSX - I will try to add one in the next verson though because this problem has come up several times. There is an identification string near the start of the BIOS that I can probably check.

[ripper713]

Since there are only so many bios images available, would it make more sense to do a checksum type validation? This would help detected corrupted or compressed bioses.

[Ultima]

A checksum based validation doesn't sound good, IMHO. That entails that you get every single BIOS and their checksums. From what I can tell, there are at least 20 different BIOS versions (that's probably an understatement). Just general validation based on file signature/header/whatever sounds fine to me as pSX Author is probably going to do anyway. And what if (hypothetically) someone made a homebrew BIOS (maybe grabbing the one from PCSX and making it standalone or something)? Then that wouldn't pass pSX's checksum validation, even though it (presumably) wouldn't be corrupt. I understand, there's likely no one developing a BIOS, but hey, the possibility's always there, and forcing the emulator to read only "sanctioned" files doesn't sound good to me.

[patrickp]

I guess it might work if there was an option to bypass the checksum validation, Ultima. pSX Author's idea of checking an ID string would detect whether it was an actual BIOS (I wonder whether he would also have to get IDs for all BIOSs, or would checking that they conform to a specific format/range be Ok?) but not necessarily whether the file is corrupt.

But it would be simpler and probably adequate in the vast majority of cases to use the ID check, I suppose.

[Ultima]

Yeah, I know it wouldn't check for corrupt files, but at the risk of having users complain when their BIOS is corrupt, at least it's a vast improvement over the current situation, and I think that's probably enough. Chances are, if someone has a valid BIOS file, it's not going to be corrupt anyway. I guess an option do enable/disable would be fine, but it's a lot of work (gathering and using the information) for only marginal gains.