Hyperspin on External Hard Drive

[wmed]

Good evening all,

I'm writing this post to have some more knowledge about setupping an external Hard Drive to launch Hyperspin.

 

I've made a 29 systems Hyperspin with RocketLauncher.

Everything is running smoothly.

I wanted to put everything on an external hard drive to use it with friends somewhere else.

Every path in RL is a Relative Path ..\, but it seems that it doesn't work at all.

Random errors like "Remove . from your extensions", "Couldn't load *.dll" on DeMul..

It seems that it's better to restart from scratch setting everything.

 

Can someone of you give me a hand at least to try to understand more about it?

Thanks a lot.

 

W

[rastan]

Well the problem with using hyperspin on other people's systems is you never know what their system is.. what they have installed... they may not have a .dll on their system that was required for the emulator... their graphics setup may be different.. some emulators are real pains in the ass with that kinda stuff.. especially demul. other than that if everything is on the external drive and all paths are correct.. technically it should run off somebody else's system with no problems but again... if your system meets all the requirements to run the emulators and the other person's system doesn't meet those requirements.. that's where you run into all kinds of problems and one of the main reasons why nobody likes pre-configured hyperspin sertups.

[wmed]

Dear rastan,

I definitely got the point.

Do you know if there's a detailed list of "needed stuff" to run HS correctly? (Like Visual++ Libraries, .dll files..)
At least I can re-order my external Hard Drive with all the programs I need to avoid the waste of time trying to fix every error a time.

 

Thanks

[rastan]

Dear rastan,

I definitely got the point.

Do you know if there's a detailed list of "needed stuff" to run HS correctly? (Like Visual++ Libraries, .dll files..)

At least I can re-order my external Hard Drive with all the programs I need to avoid the waste of time trying to fix every error a time.

 

Thanks

 

it's not so much hyperspin that you need to worry about but the actual emulators that are being used... my advice check the websites for those emulators and see what requirements are needed. getting the emulators to work outside of hyperspin first is probably the best route... it could be as simple as running each emulator outside of hyperspin and changing the configs to match the new system.

[wmed]

Ok perfect!
Thanks a lot

[epayson85]

You are more than likely going to need to setup each emulator again. Just being honest. Most of the programs create a config file when they first launch. You will see a lot of them even record GPU information. When you run it on a different computer and it can't find that GPU the emulator will either crash or erase all your screen settings. If it's crashing you will need to delete the config file and start over. It's pretty easy to go through launch each emulator, and make sure all your settings are there / the emulator is working but when ever I migrate hyperspin to a new system this is a necessary step. Plus if you use different controllers you will want to do this anyway.

[rastan]

You are more than likely going to need to setup each emulator again. Just being honest. Most of the programs create a config file when they first launch. You will see a lot of them even record GPU information. When you run it on a different computer and it can't find that GPU the emulator will either crash or erase all your screen settings. If it's crashing you will need to delete the config file and start over. It's pretty easy to go through launch each emulator, and make sure all your settings are there / the emulator is working but when ever I migrate hyperspin to a new system this is a necessary step. Plus if you use different controllers you will want to do this anyway.

 

yup, also some emulators actually store information on the C: drive in the documents or somewhere locally on the C:

[JoyStickKilla]

There are only very few emulators that do that so shouldn't be a hard thing to fix. 

[wmed]

Thanks guys.

So, at the end, the procedure would be:

- Copy Systems' Databases/Roms;

- Re-configure each emulatore like I did with this system to let them run on the new computer;

- Play.

 

Right?

I'm checking if I need some Microsoft tools for each emulator, but it seems that everything is ok.

 

Thank you

[rastan]

Thanks guys.

So, at the end, the procedure would be:

- Copy Systems' Databases/Roms;

- Re-configure each emulatore like I did with this system to let them run on the new computer;

- Play.

 

Right?

I'm checking if I need some Microsoft tools for each emulator, but it seems that everything is ok.

 

Thank you

 

as long as you get the emulators running and the paths are all setup in RL... you shouldn't run into any problems. the problems come when the emulators don't run on the new system. like when people by a pre-configured harddrive... the person that sells them the drive has it working perfectly but when they sell it to someone.. the buyer doesn't realize they have to actually configure to some the emulators. 

 

Mame is probably one of the few emulators that is universal for the most part unless somebody setup a bunch of different controls... you can throw that on any system and it works.... especially if the controls are just some generic USB controller. 

 

Good luck!

 

I'm actually in the process of moving my HS to a external drive.. when I originally set HS up... I put it on my C: drive but I had all my roms and game video snaps on a external drive... it probably won't be such a big deal for me because I just need to copy stuff and change paths in RL but even that is going to be a pain in the ass with 60 something systems... so I'll just move one system at a time.

[phantasy]

I'm also doing the external drive thing. I am perhaps over-ambitious, but once I have a windows build set up on it I plan on a Shield TV setup, and try my hand at a linux setup. If I stick with MAME and Retroarch as my primary tools, I may only have 'diet HS' on platforms where the gpu isn't strong enough or 32/64bit differences.  If I can streamline them to just have different launch icons I will feel a major success has been made. Would be great as icing to have it work with a wii for non-hs emulation by the same rom paths.