|
Post by patrickp on Aug 16, 2006 18:43:18 GMT -5
Ultima: Well, version 1.03 works after a fashion, Ultima - it still doesn't see my BIOSs, but scph1001.bin is now the default, so it doesn't mess anything up! The Disc: box still only allows Image selection, not Drive. I've tried it on two machines: both have images, save states and memcards in non-default locations, but BIOSs in the default bios subfolder in the pSX folder. One's a W2K box and one is running W98SE. Works the same on both. @herra: do you actually see a list of your own BIOSs in the dropdown BIOS: box on the Advanced tab? And, similarly, do you get the option to select Image or Drive in the Disc: box on the Basic tab?
|
|
|
Post by Ultima on Aug 16, 2006 19:29:19 GMT -5
I really don't know what to say... There is absolutely nothing different (besides whitespacing for readability) between v1.01 and v1.03 in terms of the disc dropdown thing, quite literally. v1.02 had one minor change, but I realized it was a mistake, and reverted it. As for the BIOS... are the BIOS files named like in the dropdown menu (SCPH1001.bin, SCPH7502.bin, etc), or are they different (like hyphens, spaces, underscores, or whatever)? I check if a file exists before adding it to the dropdown by splitting the dropdown item with a space as the delimiter (so the item containing "SCPH1001.bin (US)" becomes an array containing "SCPH1001.bin" and "(US)", for example), and then I just take the first element in the array (being SCPH1001.bin in this example) to check. (Those are all actually renamed copies of SCPH1001.bin, FYI ;P) Edit: [FIXED IN NEXT VERSION] Just noticed an odd little bug though... DTLH3000.bin doesn't show up in the full dropdown list. Nothing major, but still... O.o
|
|
|
Post by Gamesoul Master on Aug 17, 2006 6:41:07 GMT -5
Yeah, I noticed it wasn't showing up in the list before setting the .exe path, especially since that was the last BIOS file I had been using. I haven't had any problem in any version (except DTLH3000.bin, of course) with it showing the BIOS files in the list, nor any problem with it showing (and using) "Image" or "Drive" selections. All that works perfectly fine for me. However, it *didn't* find SCPH101.bin, which is sitting there with the rest of my BIOS files (and it *was* on the list before setting the .exe path).
I'm completely clueless as to why you can't use long filenames. No matter what programming language I'm using, I've never even had a thought in my head about having to use short filenames, because there's never been a need for it. Is this some kind of limitation of programming in that AutoIt variation of Basic?
I'm not sure I wanna know how you're getting .ini entries if you're not using that function. Before I started using it, I was using things like string-search functions and other crap like that. The thought still makes me shutter. Now I definitely wanna see your source code if you ever decide to release it.
|
|
|
Post by patrickp on Aug 17, 2006 7:56:23 GMT -5
@gamesoul Master: Long filename limitations are a characteristic of DOS versions before the W2K one (AIR the w98 version was v7 or 7.x). My guess is that AutoIt must be based on that. I think a lot of people still prefer the older DOS versions since they feature a lot more, and more useful, commands for working with it as a stand-alone, rather than as an add-on to Windows. Ultima: I think I have a partial explanation of what's happening with the v1.03 BIOS selection; IIRC I originally said it still showed SCPH1001.bin as the only option after I selected the pSX executable location. That was me being dozy. In fact, it shows SCPH1000.bin (JP), which I thought I had, so I looked in my bios folder. Yes, it was the first one listed. So I moved the first few somewhere else, went back and re-started v1.03 and, sure enough, it showed what was now the first BIOS in the list - but still, only that one. So it _is_ looking in my bios folder now, but only seeing (or presenting) the first one. As for the Disc: options - no idea. I went back and checked the old versions: The original version (unnumbered, but let's call it v1.00) showed Image and the G: H: and I: drives as options - those drives are my two optical drives and my virtual drive correctly listed, so full marks for that (on my system...) Version 1.01 showed Image and Drive as options: if I selected Image (after selecting the pSX executable) the browse button took me straight to my image folder (the one I use, on another drive); if I selected Drive, the browse button showed all my drives. Also full marks! Howver, on versions 1.02 and 1.03, the only option offered is Image. If I navigate to a drive with a Playstation disk in it , it shows the contents but doesn't let me select the drive - as you would expect for the Image option. The same occurs on both of two machines, one running W2k and one running W98SE. Edit: yes, all my BIOSs are standard ones with the correct names, and no spaces/additions, except that I also have a copy of SCPH10000.bin (?).
|
|
|
Post by Ultima on Aug 17, 2006 8:05:15 GMT -5
@gamesoul Master: Full names isn't a limitation with the language, I said that if (for example) someone moved their memory card folder to Memory Cards, it will have a space in it, regardless of where it is in the hard drive. As such, I cannot use it in the commandline because of a limitation with pSX, which doesn't allow spaces when selecting memory card files by commandline.
As for the INI stuff... AutoIt provides functions for reading INI files (as I said before): IniDelete, IniRead, IniReadSection, IniReadSectionNames, IniWrite.
And I just fixed a few more things with the BIOS stuff, so it finds SCPH101.bin correctly now.
|
|
|
Post by Gamesoul Master on Aug 17, 2006 8:06:52 GMT -5
patrickp: SCPH10000.bin is the first japanese PS2 BIOS image, in case you put that question mark there as a question to it. Ultima: Then why don't you just add the Memory Card options to psx.ini, which has no problems with spaces?
|
|
|
Post by Ultima on Aug 17, 2006 8:10:45 GMT -5
Because there's a shortcut export feature that would need memory card in the commandline, otherwise I might've done that as well Seeing as how it's more of a limitation with the emulator itself, I'd say it'd be easier (well, I don't know if it's easier, but at least it's better) to fix the problem on that end than mine. patrickp: Hm. Odd that it only shows one item per combobox on your end though, which indicates to me that there might be something else wrong on your end. I'll check what I changed between 1.01 and 1.02 again, I guess.
|
|
|
Post by Gamesoul Master on Aug 17, 2006 8:16:41 GMT -5
Ugh... a fine example of how extra features can actually decrease base functionality. That makes it unfixable, unless you wanna try talking to microsoft about fixing the problem (as it is "their" command-line functions that are at fault, not the emulator).
|
|
|
Post by Ultima on Aug 17, 2006 8:19:21 GMT -5
Yep. pSX Author could always write his own commandline parser, IINM, but then that'd make it not-so-easy anymore xD
|
|
|
Post by Gamesoul Master on Aug 17, 2006 8:23:08 GMT -5
It'd be too much of a pain to implement something like that, but it might be worthwhile, if you figure that since he added support for specifying a memory card in command-line, he might as well make that aspect as compatible as possible.
Edit: If a second program is written that simply takes the whole command-line string called from the shortcut, picks out the full memory card aspects, writes them to psx.ini, and then calls psxfin.exe with the other specified command-line options, that could work...
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 17, 2006 8:26:34 GMT -5
|
|
|
Post by patrickp on Aug 17, 2006 8:31:03 GMT -5
patrickp: Hm. Odd that it only shows one item per combobox on your end though, which indicates to me that there might be something else wrong on your end. I'll check what I changed between 1.01 and 1.02 again, I guess. Seems to me to be more likely (since I get the same results on two different machines running different versions of Windows) that it might be something M$ changed from W2K to XP - asuming you and others commenting here are running XP?
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Aug 17, 2006 8:33:54 GMT -5
I'm running XP for one. Don't have a spare comp with other OS' to test this, unfortunately.
|
|
|
Post by Gamesoul Master on Aug 17, 2006 8:41:12 GMT -5
patrickp: Quick thing to try. Open up the frontend's config file, and change "DiscType=Image" to "DiscType=Drive" (change the one listed under [Last Session]), then start up the frontend and see what happens. Edit: I am also running XP, as is my other computer (I wish I had kept w2k on it for purposes like this, not to mention I find w2k to be superior in every way except not being compatible with XP software).
|
|
|
Post by patrickp on Aug 17, 2006 9:31:14 GMT -5
@gamesoul Master: yes, that changes the Disc: selection to Drive; it also behaves like the drive selection now, i.e. it shows my drives when I click the browse button. It doesn't show the Image option now, of course. Also, Ultima, I mentioned a little while ago that, after selecting the pSX executive, it now showed SCPH1000.bin (JP) as the BIOS, which was the first one in my bios folder, and when I removed a few so a different BIOS was first, it showed that one. Seems to have stopped doing that: it just shows SCPH1001 (US), regardless of what's in the bios folder, and that can't be changed - not by editing the .ini file, either.
|
|