Post by: dl0n3_1_wahks_0n on June 05, 2004, 04:49:00 PM
), ohhhhhh are there any screen shots of X-select 0.6 so i can get an idea of what it is before i start using it?thanks
peace
Post by: Henne_C on June 06, 2004, 07:02:00 PM
Post by: BloodyMary on June 07, 2004, 08:50:00 AM
| QUOTE (dl0n3_1_wahks_0n @ Jun 5 2004, 08:49 PM) |
| does X-select 0.6 display text on LCD screens hooked up to SmartXX modchips? this would be really sweet! especially when i read that X-select 0.6 is simple use dashboard with no graphics (no lagging, weeeee ), ohhhhhh are there any screen shots of X-select 0.6 so i can get an idea of what it is before i start using it? thanks peace |
If you want the clean and simple with few bells and whistles..
I'd have to say evox is your best bet...
Post by: BenJeremy on June 08, 2004, 07:46:00 AM
In retrospect, it could add several small (to keep load times down) icons to represent all of the different dashboards, as well as a generic one for other apps.
Perhaps some procedural imaging to spice things up...?
My intention was to keep it very tight and unobtrusive, though, as a selector goes. Adding too many things to it would bog things down. It should never have too much stuff going on - after all - if you want a ton of bells and whistles, that's what full-blown dashboards are for!
Post by: blittan on July 17, 2004, 02:17:00 PM
Post by: nezff on August 03, 2004, 11:18:00 AM
Post by: TOOGAM on August 03, 2004, 03:13:00 PM
(I notice Exusers UnleashX Installer CD v3.1 comes with XSelect 0.6 but Iriez posted the new version of the CD less than half an hour after he posted of XSelect 0.9 so I'm guessing the CD maintainers may have made the CD before knowing about the new version. But then again, they do call it "XSelect 0.6", which is more consistant with the name that 0.9 uses.)
And while I'm discussing this program:
The subtitle of this thread says "Bug reports here!" I've tested and found that, as 0.9's docs state, the simple presense of a *.XBE file with a very long name in E:\ would cause a major problem seeing the Config Dashes screen (even if that program wasn't listed in the dashes.txt file). Ends up being quite horrible, actually. It seems that the rest of the changes in 0.9's change logs aren't so much bug fixes, as new features or improvements, but not really bugs.
I don't know that the other "bugs" reported in this thread are X-Selector 0.6's fault. For one, the D: often refers to the current directory of a launched title, rather than the DVD Drive, hence the ID_No_D_Mount option that Evolution-X RemoteX can see in the evox.ini files. It probably depends on how X-Selector is launched.
And I dunno about that issue blittan has with the Cozmo RF controller. I suspect it is more likely an issue with IGR which has become infamous for incompatibilities. If your IGR involved you pressing some key combination, maybe by pressing those buttons you ended up telling X-Selector to run some other program by default (possibly itself, or something that caused an Error 21 which the IGR code could cause to re-run X-Selector again).
X-Selector seems to be pretty bug-free from what I can tell, other than the issue of a really long filename in the older versions. The program probably just doesn't have much opportunity to have a lot of bugs since it is a fairly simple program.
0.9's text file has a misspelling "formtted".
So, is this topic going to be renamed to XSelect 0.9 (or a new topic started)? Seems there wasn't much conversation (averaging less than one page of discussion in four months since July 10, 2003) about the old versions, even on a pinned topic.
July 10th, 2003 post says Gigabyte and another author will be new author. June 8th, 2004 post says Muerte has the source (which was available at the usual place right by the old versions of XSelect). X-Scene News says 0.9 was made by "a new author", but doesn't say which of these two, or if it was someone else entirely. At very least, it seems there may have been multiple authors looking at this.
Has there been any progress since 0.6 by some authors that isn't in 0.9, and if so, will their changes be based on the 0.9 source or would people need to pick and choose versions? (PBL seems to have become a mess lately, with Metoo, Frosting, PBL Lite... and even before that there was 1.4 which was made by a different group, 1.3.5i which was supposedly an internal build leaked). I'm wondering what BenJeremy knows/thinks about what the future holds for the software now. And BJ, will you admit to being an author of 0.6 or 0.5?, 'cause in this thread you kinda sound like this has been your project but none of the software versions seem to have any authors names in them.
Post by: nezff on August 03, 2004, 03:28:00 PM
Ok first of, I WAS asking about upgrading 0.6 to 0.9. i ASKED if i could just upgrade 0.6 with a new xbe like the one from 0.9 and just not change anything else? is this ok to just do this? not sure i used the firefuckers install disc and it is pretty cool. What i need to know is will it be ok to just upgrade the xbe or is there something else that needs it also?
Post by: TOOGAM on August 03, 2004, 08:08:00 PM
The answer is: Probably. Just replace the 0.6 XBE file with the 0.9 XBE file and all will be fine with just one possible exception: Possible issues related to XBE signatures. Other than that, replacing the XBE will work painlessly.
Since the hacks I prefer use Habibi signatures, there was no issue for me. I can give you some advise to find out if signatures will be a problem. Of course you take this advise or ignore it at your own risk: Don't blame me for you not knowing how to handle signature issues.
If you did use the old font hacks or whatever, then all you need to do is make sure 0.9 is signed using the same digital signature that your copy of 0.6 uses, and then you can replace the file just fine. I have no idea what digital signature gets used with the install disc you're referring to.
You can test with more certainty is to run 0.6, and then see if you can run any executable from 0.6, or if you can only run certain files like Phoenix BIOS Loader. If you can run a version 0.9 directly from version 0.6, or if you can run a dashboard directly from 0.6 and then run 0.9 directly from that dashboard without doing anything else fancy like running nkpatcher for Phoenix BIOS Loader between when 0.6 launched the dashboard and when the dashboard launched 0.9, then you should be fine.
As long as you're not using an old font hack, it likely won't matter, but I don't know what the install disc you're using uses.
If you're using a mod-chip and you use an alternate BIOS, that BIOS likely has signature checking disabled, so you should be fine replacing the files.
Post by: macel on August 13, 2004, 01:09:00 PM
Post by: TOOGAM on September 06, 2004, 10:12:00 AM
Passwords don't work in 0.9. NeoNitiPheus pointed this out in his forum post. My conclusion: bHasPasscode = LoadPasscode(); runs before g_PassCodeFileToRead is set, and changing if ( bHasPasscode ) to if ( LoadPasscode() ) would fix that.
E:\UDATA\01010001\0123456789ABC\ is not a standard saved game name, because 0123456789ABC is 13 hexidecimal characters long, not 12. The version of the MS Dash on my Xbox seems to not care, but I recall my version copying saves without some icon files, and this did not work on my friend's Xbox. I suggest future versions should look for stuff in E:\UDATA\01010001\0123456789ABC\ as well as E:\UDATA\01010001\, but use E:\UDATA\01010001\0123456789AB\ as its main directory.
| QUOTE (macel @ Aug 13 2004, 09:05 PM) |
| I don't like how the 0.9 assaults my screen with the huge box telling me how to enter the config screen.. it's completely unnecessary and mighty ugly. Went back to 0.6 goodness for that, although I liked the reduced wait time of 0.9. |
I for one like how XSelect 0.9 visibly gives directions on how when to press the configure buttons, which is also when to press any other buttons to run another dash. It's better than run writing some small text which, depending on the background (such as the blue-and-white Evox2.Jpg), may not be quite as noticable. I really disagree with macel's choice to use the half-done version 0.6 over such an issue, perhaps because I'm just biased and am also disagreeing with his choice on which method is better. To each his own, I guess. I do think the other advantages (namely being fully self-configurable) outweigh that, at least for my uses. XSelect 0.9 have saved me and a friend of mine from needing to re-run the saved game exploit (very good for my friend who now lives in an other state and didn't have a commercial game to use an exploit).
Still, to make XSelect 0.9 run like the old version in that respect, one simply would need to change the "\r\r(Press Left and Right" to "\0\0(Press Left and Right", and change the call to RenderMessageBox() in the next line of code so it passes false on the next line. The first part of this could be done by hex editing (search for "Configure" and modify the bytes a bit before it), and then re-signing to be Habibi again would probably be needed. The second part may require changing just one bit (or optionally byte) in the executable from 1 to 0, but I don't know which bit that would be, so I'd suggest just re-compiling with the XDK to make that change. I do hope that macel's suggestion to remove the border is NOT taken as I prefer the other way. But perhaps this could be a configurable option (similar to how XSelect 0.9 handles SHOWPATH.NUL: whether a zero-byte file exists.)
(Hopefully all this is done while keeping the XBE file at 256K of less. I have a memory unit image I like which has 0 bytes free so I hope any new XSelect doesn't grow in size.)
What else have I found? The author of X-Selector (which would be version 0.6) is reported to be "BenJermy", confirming my earlier thoughts from this thread. (I'm guessing that's just a misspelling of his name on that other page, especially since that page and this thread, IIRC, show BenJeremy as responsible for both this program and MXM.) I still wish BenJeremy would have responded in this thread to my questions about the future of this program. Ah well. I guess now there may be two publicly unknowns (whoever made 0.6 and whoever made 0.9).
I've looked around the source a bit. I myself am considering making a clone of XSelect using the OpenXDK. Since XSelect seems to use DirectX, and I'm guessing the OpenXDK may not, I figure I may as well release the program under an entirely different name, which I haven't decided on yet. Does anyone have anything they would like to see in XSelect's future? (Keeping in mind that one of XSelect's chief features is a small size, so adding tons of unrelated niceties may not belong?) I think the one new feature I'd like to see, which apparently would be extremely small, would be to build in nkpatcher to have an option to nkpatch before running the executable. Then XSelect could have signing, and a program with nkpatcher's functionality wouldn't be limited to what it runs.
Post by: EvilWays on September 08, 2004, 03:16:00 AM
Post by: FBF on September 08, 2004, 01:30:00 PM
| QUOTE (TOOGAM @ Sep 6 2004, 06:15 PM) |
| I've looked around the source a bit. I myself am considering making a clone of XSelect using the OpenXDK. Since XSelect seems to use DirectX, and I'm guessing the OpenXDK may not, I figure I may as well release the program under an entirely different name, which I haven't decided on yet. Does anyone have anything they would like to see in XSelect's future? (Keeping in mind that one of XSelect's chief features is a small size, so adding tons of unrelated niceties may not belong?) I think the one new feature I'd like to see, which apparently would be extremely small, would be to build in nkpatcher to have an option to nkpatch before running the executable. Then XSelect could have signing, and a program with nkpatcher's functionality wouldn't be limited to what it runs. |
I for one would like to see a menu saying
| CODE |
Press A for XXXXX Press B for XXXXX |
As I cant always the buttons for 8 different dashes/apps
but from the other posts in this thread it seem this would not be popular.
Post by: GunPR on January 19, 2005, 03:44:00 AM
Post by: PSPumpgun on July 22, 2006, 12:16:00 PM
Post by: Evox117 on July 22, 2006, 07:40:00 PM
Post by: DreCon on July 28, 2006, 06:45:00 PM
Post by: BenJeremy on July 09, 2003, 07:14:00 PM
X-Select (0.6)
What is it?
- X-Selector is an application that you set as your primary booting dashboard, and it will also allow you to set a password and assign quick-button selections for dashboards and applications you use the most for almost-direct booting.
Directions:
- 8 Dashboard selections, assignable to a button on the game controller.
- Because of issues with the input routines, you must press the gamepad button when the brief message pops up on the screen.
(Sorry, tried to do it differently, but the gamepad refused to see buttons pressed before the app is running)
- Right-Trigger, by itself, brings up the Dash Quick-Pick menu, allowing you to quickly select the 'default' dashboard.
- Left-Trigger, by itself, brings up the application Quick-Pick menu, for fast selection of your top games or apps.
- Without input, Boots the last dashboard selected with Right-Trigger+<Button> or via the Quick-Pick menu.
- Holding a button will result in the booting of the dash assigned to that button (though it does NOT set it as the default)
- Holding a button, with the Right-Trigger, will result in the booting of the dash assigned to that button and select that dashboard as the default.
- Holding a button, with the Left-Trigger, will result in the booting of the application assigned to that button
- START held will result in display of the configuration menu.
- You can assign a new password
- You can select new dashboard assignments
Installing:
NOTE: Backup ALL of your files, and make sure you have a valid bootable dash [MXM, Evo-X or Avalaunch] disc handy)
You alone are responsible for anything 'bad' happening. If you are unsure about what you are doing, then don't do it.
1. Copy XSelector.xbe to your boot partition (usually C:, unless you're using a BIOS that changes this)
2. Rename your primary Dashboard to something else (For example, if your BIOS boots "evoxdash.xbe", rename it "evox.xbe")
3. Rename "XSelector.xbe" to the same name the BIOS boots as the primary dashboard (in the above example, rename "XSelector.xbe" to "evoxdash.xbe")
4. Reboot.
Files used (Look in E:UDATA 1010001):
dashes.txt
- Dashboard slots, 8 lines of dashboard applications, with drive/paths, Corresponding to buttons: A, B, X, Y, Up, Down, Left, and Right.
apps.txt
- Application slots, 8 lines of application filepaths. Launched when the Left-Trigger is used with the corresponding buttons: A, B, X, Y, Up, Down, Left, and Right.
Example "apps.txt":
-----Between these lines------
F:EMUSPCSXdefault.xbe
F:EMUSSNESdefault.xbe
E:GAMESX-Marblesdefault.xbe
E:GAMESSENSEXdefault.xbe
E:APPSBOXdefault.xbe
E:APPSDVDRX2default.xbe
E:APPSFlashXdefault.xbe
E:APPSXCOMMdefault.xbe
-----Between these lines------
lastdash.txt
- The path to the 'default' dashboard. This will be changed when the Right-Trigger is used with the Dash button, or when the "Quick-Pick" menu is brought up.
passcode.txt
- This is the passcode used for the Xbox. There is a default password as well. Do not set this file manually... use the configuration menu.
What's New?
----0.6----
* Name Change (the new authors will be taking over, wanted to change the name)
* Time Check performed on bootup to avoid hassles when clock is reset after a long period with the power disconnected.
* Boot to DVD option added
* Signed for Font Exploit
What's Next?
- Understand more dashboard types
- Add the ability to tell the versions of recognized dashboards
- Include some means to set up the application slots
- Modify launch procedure to have dashboards launch as TRUE dashboards (undocumented calls)
- Small 3-D "bug" instead of boring text when X-Selector is waiting for user decision on startup.
Post by: EvilWays on July 09, 2003, 07:50:00 PM
Post by: BenJeremy on July 09, 2003, 05:54:00 PM
| QUOTE (EvilWays @ Jul 9 2003, 09:50 PM) |
| Who will the new author(s) be? |
"Gigabyte" and another author (who doesn't have a pseudonym yet)
Both are good friends and colleagues from work. Both are excellent software engineers with abilities that I'd put against anybody out there.
Post by: chilin_dude on July 16, 2003, 11:09:00 AM
Post by: BenJeremy on July 16, 2003, 11:16:00 AM
| QUOTE (chilin_dude @ Jul 16 2003, 01:09 PM) |
| Not really a bug but The XBE auto name is still X Selecter 0.5 when really it should be 0.6! |
Doh!
Thanks...
Post by: Slipknot6d9 on July 17, 2003, 05:39:00 PM
Post by: cdjstyle on July 28, 2003, 01:54:00 PM
Post by: no.7 on July 29, 2003, 09:03:00 AM
I will tell you why, even if you don`want to hear it hehe.
i posted my problem here:
http://forums.xbox-s...4&hl=widescreen
but got no answer, i also posted at http://xboxmediaplayer.de/ and still no good solution came forth.
the problem: if i set xbmp to autodetect settings, and put widescreen in m$ dash. All i get is a skin.xml error message. And since ive used xbmp as a dash this is very frustrating.
XBMP wouldnt load if i set it to constant PAL 16:9
Setting xbmp to PAL 4:3 worked with m$ set to widescreen, but then xbmp wont boot when i used the enigmah video converter. Another problem was that games wouldnt load in widescreen from xbpm.
As you can guess all of this got very frustrating when moving the xbox to a another place that has widescreen but no pc.
This app is a good lifesaver so you can always be able to boot with evox whenever xbmp acts up. All i wish is that xbmp at sometime can be able to detect settings etc like evox.
Post by: BenJeremy on July 29, 2003, 09:07:00 AM
...and don't forget to try Media X Menu, if you haven't taken it for a spin lately (or ever). It's even more painless with X-Select.
Post by: no.7 on July 29, 2003, 11:57:00 AM
before i had to go to evox from xbmp, then launch it. just keeps getting better.
i tried Media X Menu the first time it was available, truthfully it didnt suit me.
maybe ill give it a try to see if it has changed since then, probably has hehe.
Post by: * illusion * on July 30, 2003, 01:01:00 PM
Post by: Budmiester on July 31, 2003, 06:27:00 AM
It may be because I have coloured X image and LED and such, but half the time it reboots flawlessly but sometimes itll just sit there blinking X-select at me (either indefinitely or after a few it finally boots.) Happens most often from XBMP.
Cheers, handy little app. Tho I would like to just set dashes by editing the txt files, because it doesnt support all of them.
Post by: BenJeremy on July 31, 2003, 06:28:00 AM
| QUOTE (Budmiester @ Jul 31 2003, 08:27 AM) |
| Im having weird IGR experiences with X-select. It may be because I have coloured X image and LED and such, but half the time it reboots flawlessly but sometimes itll just sit there blinking X-select at me (either indefinitely or after a few it finally boots.) Happens most often from XBMP. Cheers, handy little app. Tho I would like to just set dashes by editing the txt files, because it doesnt support all of them. |
Well, Team Executer acknowledges there are issues at times with IGR, mostly to do with the activity currently going on when activated.
IGR is still an imperfect science, at best, on the Xbox.
Post by: rob1309 on August 07, 2003, 10:08:00 AM
| QUOTE (Slipknot6d9 @ Jul 17 2003, 06:39 PM) |
| when i do IGR with X-Selector on it takes a temporary picture of whatever i'm doing and then says s-selector in the foreground. WHat am i supposed to do if i am watching porn on XBMP or playin DOAX w/ nude hack?? Is there any way to make it just have a black background or somethin when i IGR?? |
lol thats funny man
anyways, is there a chance anyone will add remote support for it? for instance password: 1391
or whatever combo? kinda like directv unlock stuff?
cuz sometimes when i take box downstairs i only bring remote cuz i plan on watching movies and vids but i want xbmp to be pass protected
but in current state, i still love xselect
Post by: gultig on August 20, 2003, 08:04:00 AM
| QUOTE (rob1309 @ Aug 7 2003, 07:08 PM) |
| anyways, is there a chance anyone will add remote support for it? for instance password: 1391 or whatever combo? kinda like directv unlock stuff? cuz sometimes when i take box downstairs i only bring remote cuz i plan on watching movies and vids but i want xbmp to be pass protected but in current state, i still love xselect |
That would be a great feature. You don't know how many times I've sat down to watch a movie only to have to get up, find a controller, plug it in, and then put in the password.
Either having the ability to enter the password from the remote, or having a preselected app boot (XBMP) when a button is pressed on it would be cool.
Anyway, great work on this app! I wouldn't run my xbox without it.
gultig
Post by: BenJeremy on August 27, 2003, 12:22:00 PM
| QUOTE (yoshi98bc @ Aug 27 2003, 03:47 PM) |
| Well, I can't seem to bring up the config menu when I hold start. Am I missing something. Also, with in game reset, it always resets to the default dash. I use x2 bios 4977. Just a couple of things I noticed. |
Try hitting both triggers instead. One, then the other, when the "X-Select" appears (should see dots appear as you hit the triggers)
Might be a controller issue, as the "S" controllers are a bit funky for some odd reason.
Post by: GEoMaNTiK on September 19, 2003, 08:17:00 AM
Since around the time of installing X-Select 0.6 I've been having probs accessing the DVDROM contents via FlashFXP.
On accessing D: I would only get the contents of the C: Drive, after much playing around, ie. Refresh, ejecting and so on I couldn't get it to work.
I removed X-Select and made Evox the boot xbe and I could see my DVDROM contents again, just to make sure I put X-Select back again as the boot xbe and again the D: drive was back to displaying as C:
btw I'm using x2lite 4973
Post by: BenJeremy on September 19, 2003, 09:55:00 AM
| QUOTE (GEoMaNTiK @ Sep 19 2003, 12:17 PM) |
| I'm not sure if this is a bug or not... Since around the time of installing X-Select 0.6 I've been having probs accessing the DVDROM contents via FlashFXP. On accessing D: I would only get the contents of the C: Drive, after much playing around, ie. Refresh, ejecting and so on I couldn't get it to work. I removed X-Select and made Evox the boot xbe and I could see my DVDROM contents again, just to make sure I put X-Select back again as the boot xbe and again the D: drive was back to displaying as C: btw I'm using x2lite 4973 |
I'm guessing it's a bug in Evo-X.
It doesn't like running as an app for some reason (which is what X-Select must do) There is a difference in the way the system launches an app vs. a dashboard, and how it is set up when it starts up. Evo-X doesn't take the time to recognize the difference, apparently, only expecting to boot up as a dashboard, so it fails to map D: properly.
MXM shouldn't have this problem.
I'm playing around soon with the launching of apps, and any breakthroughs will carry over into X-Select (i.e. launching any app as dashboard).
Post by: rob1309 on September 19, 2003, 01:24:00 PM
| QUOTE (GEoMaNTiK @ Sep 19 2003, 11:17 AM) |
| I'm not sure if this is a bug or not... Since around the time of installing X-Select 0.6 I've been having probs accessing the DVDROM contents via FlashFXP. On accessing D: I would only get the contents of the C: Drive, after much playing around, ie. Refresh, ejecting and so on I couldn't get it to work. I removed X-Select and made Evox the boot xbe and I could see my DVDROM contents again, just to make sure I put X-Select back again as the boot xbe and again the D: drive was back to displaying as C: btw I'm using x2lite 4973 |
yea i had same prob
not an issue with xselect or evox i don't think as i tried lots of things to fig it out
my results:
old bios- d showed correctly via ftp and file manager of avalaunch
new x2 bios- d showed as C contents via ftp but showed fine in file manager of avalaunch
evox showed d as c with x2 bios too
the x2 bios i'm referring to is 4977
older bios i tried was evox d6...think i also tried the debug bios too, the 4627 one
Post by: BenJeremy on December 01, 2003, 11:39:00 AM
| QUOTE (Alekz @ Dec 1 2003, 01:20 PM) |
| i got a question concerning the new UnleashX release and IGR.... does x-select support IGR? if yes, hacked msdash and Unleash would support this function too.... i love unleash and my modded msdash but i only ave an old xecut0r,... so no chance to get a bios supporting igr, is it possible, or easy to add this function to x-select? |
Hmmm... well, when MXM supports it, so, too, will X-Select (which needs to get updated soon for including Unleash(ed)X in the known dashboards list (though it should still support it fine)
IGR involves patching the BIOS. I'll bug the expert on BIOS patches again when I get a chance.
Post by: BenJeremy on December 01, 2003, 05:27:00 PM
Post by: upup on December 12, 2003, 09:31:00 PM
Update: Thanks. also great program.
Post by: BenJeremy on December 13, 2003, 05:26:00 AM
| QUOTE (upup @ Dec 13 2003, 01:31 AM) |
| is there an way i can launch my other dashboards from a folder off of the f drive? for example (f:dashboardsmxmmxm.xbe)? thanks for the help |
It's described in the readme... you just have to manually edit the dashes.txt file to put the full path (Location will show up as "other" since I didn't want to try and display potentially long paths in the menu display)