djvj
-
Posts
2,069 -
Joined
-
Last visited
-
Days Won
1
About djvj
- Birthday 11/16/1979
djvj's Achievements
-
Moving the list to the RL forum since I won't be updating this one here: http://www.rlauncher.com/forum/showthread.php?2803-Best-Emulator-For-Each-System
-
Version 1.0.8
1,873 downloads
Purpose: Moves roms and other Hyperspin Media that don't match your system's xml (database) out of your folders. Requires: RocketLauncher and at least one rom path set for that system in RocketLauncherUI - WILL NOT work with HyperLaunch. Hotkeys: Escape (Cancel Clean or Exit application) WARNING - This will overwrite files in the "%assetPath% (UNKNOWN)" folder if it already exists. Backup your roms and media first. Reads RocketLauncherUI Systems.xml or Hyperspin's Main Menu xml for systems Reads RocketLauncher system's Emulators.ini for Rom_Paths Logs everything to "Rom Folder Cleaner.log" Press the top ... button to define a custom xml to match your assets Press the bottom ... button to define a custom rom path to match your assets If you have multiple roms with the same name but different extensions, it will think these are good and keep these in your rom folder. ONLY works with console type roms with one file. Have not tested with roms in folders. Known issues: Mapped network drives may return garbage when reading from the path. Resolution: Run it on that pc, not through the network. -
483 downloads
Needed a tool to quickly go through my roms paths and clean them out of roms that are not found in each HS xml. So Rom Folder Cleaner was born. •It requires RocketLauncher and at least 1 rom path set up for the system you want to clean. •It will only do 1 rom path at a time. Do not ask for doing multiple, it will not happen and is too risky. •It works by matching filenames only. •It does NOT delete anything, simply works by moving files out. •Do not use this for MAME or arcade systems that have bios files in the rom path. You do not have bios files on your xml and will get moved out, breaking your games. •Read the ReadMe.txt for more information and carefully follow the prompts upon startup. If you get a approved number higher than the number of roms in your xml, it means you have multiple roms named the same with different extensions. Example: Quote 01:55:25:600 | Approved Rom - "Adventures of Lex and Grim, The (World) (Unl).7z" 01:55:25:606 | WARNING MULTIPLE ROM FOUND - Approved Rom - "Adventures of Lex and Grim, The (World) (Unl).nes.7z" 01:55:25:612 | WARNING MULTIPLE ROM FOUND - Approved Rom - "Adventures of Lex and Grim, The (World) (Unl).sav.7z" If your status is consistently "Clean ME", it means you have duplicate files and the above example log lines will be in your log for each duplicate file found. So refer to your log to find these. Just because status may say "OK", doesn't mean that everything matches. Status is calculated simply by a file count. So you may still want to clean once. If after cleaning and your status is still OK, then everything matches the xml. http://www.hyperspin...folder-cleaner/ -
336 downloads
This will adjust your Master Volume in Windows Vista/7 to any level you wish, after a set amount of idle time. It will also fade the volume down and back up to normal, rather then an abrupt change. All of this is adjustable via the GUI when you run the app. It will create the settings.ini for you automatically on first use. -
It's not breaking paths for anything that takes time to setup, they all stay the same. Nothing regarding emulators is changing. We've always supported relative paths for that exact reason. The base folder name doesn't change anything.
-
Thank you everyone. dark13, that's a bad idea only because the old exe will probably error out if ran but also start writing old settings into your ini files and make it all confusing if you ever open them up. Once instance is the daemon tools settings that changed to virtualdrive. Thats the reason the transition tool deletes the old exes automatically, to prevent this. Metal, it's actually very fast to update, I had it down to about 20 seconds here. I tried to cover a lot in the guide to eliminate confusion on steps.
-
Thanks everyone. Tom, if you have an issue, this thread is not the place for it. Nothing in the mame module or how it loads inis was changed in this update. So there might be something not configured right or you may be doing something customized that is not yet supported in the module. Please create a thread over on the RL forum if you need help. I can tell you though, the other inis are not read by the module. You would need to go over how the module works and adjust your setup to match or maybe we can figure out something to make your unique setup work.
-
Full release thread: http://www.rlauncher.com/forum/content.php?130-RocketLauncher-v1-0-Release! We are proud to announce the release of RocketLauncher v1.0! In this release, all instances of HyperLaunch have been replaced with RocketLauncher. Also what was once HyperLaunchHQ is now known as RocketLauncherUI and HyperPause is now known as Pause. As you can imagine, this was a very intensive change. Changing all references from one name to another takes a very long time to do it right. Certainly never want to do that again. In case you haven't realized, the url is now www.rlauncher.com. The old domain will still bring you to the RL site for awhile until I decide to expire it. So update your bookmarks. With this release, most of you will be happy that GIT is no more. You no longer need to be bothered installing another application to use RocketLauncher. I thank you all for putting up with it for the time until we could develop a proper method to get you updates. RocketLauncherUI now has a built-in updater that brolly did an excellent job with. Each time you launch RocketLauncherUI, and you are online, RocketLauncherUI will inform you if there are any new changes you need to download. All updates are handled internal to RocketLauncherUI. GIT will be taken down very shortly. So going forward, please use RL when talking about RocketLauncher and RLUI when talking about RocketLauncherUI. If you use HL, we will assume you are talking about an older version, HyperLaunch 2. To ease the transition from HyperLaunch v3.x to RocketLauncher, I created a Transition tool to do all the work for you. You will also find the links to the initial upgrade pack there as well. Please see this guide on how to use them. It's only a few clicks and you will be all set to use RocketLauncher: http://www.rlauncher.com/wiki/index.php?title=Transition_From_HyperLaunch3 I'd also like to thank Warham and Marxkemp from IRC that helped me test this new release.
- 27 replies
-
- 22
-
-
It says right on the front page it does not run any games, so no sense in asking about it. Now, this system is obviously too new to discuss, so please do not ask about it again.
-
Thank you. You could probably put the bios files in one zip and host it off dropbox. It won't be that big. Sent from my Samsung Galaxy S3 using Tapatalk 4.
-
Only solution is to duplicate.
-
I've already started going that route in the module section so feel free to add on to those threads. Sent from my SCH-I535 using Tapatalk 4 Beta
-
Well many of the modules might be running a little behind as I can't keep up with the constant releases.
-
I don't know enough about it to say.
-
For the most part, yes.
