@LDAWG:
That makes since It certainly is looking good thus far. What program are you using to make the installer?
Also, you might as well add the other config paths too (SPCs and screenshots) and offer an advanced section where you specify the paths to things like the BS-X BIOS and other base cartridges.
It is better to be silent and thought a fool then to open your mouth and remove all doubt
I am Zophar, Master of Sh*t!
[url=http://archlyn.bravejournal.com]View my blog[/url]
grinvader wrote:Why separate SRMs and ZSTs ? They are both saves...
I'll give you the "why not" cliched answer
Actually, some people prefer to separate like items(classification).. all saves in one folder, snapshots in another, savestates in another as well (and there's always the ROMs folder). For some people, it helps them manage these files better.
grinvader wrote:Why separate SRMs and ZSTs ? They are both saves...
Just had another wild Idea considering savestates and save ram.
I think I know where you are going with that, but I bet it wouldn't work out.
Or then it would.
whicker: franpa is grammatically correct, and he still gets ripped on? sweener2001: Grammatically correct this one time? sure. every other time? no. does that give him a right? not really.
lord alpha wrote:@LDAWG:
That makes since It certainly is looking good thus far. What program are you using to make the installer?
I'm using pretty much all free software:
WinINSTALL LE (comes on the Windows 2000 CD)
Windows Installer SDK
Orca
Visual Studio 2005
C#
VB
I may get some more tools later, to help me with MSI Scripting.
Right now it's in .MSI Format, but I will probably package the final installer as an .EXE
I just hope I can make this thing run good in Windows 95
Just a thought but why not have it install to something simpler like...
C:\Program Files\ZSnes
...and have the neccessary documents unpacked and create folders...
.\bios (for the bios roms and stuff like BS-X and others)
.\saves (music, screenshots, savestates, static ram, etc.)
.\documentation (all the how-tos and to-dos)
.\source (copy of the GPLed sources in vanilla/CVS form)
No need for unneccesary clutter, pathes, and stuff nobody will ever use that isn't directly related to ZSnes. I also wouldn't worry about a ROM folder tracker and stuff like that.
It's usually best to keep any downloadable installer/self-extractor as small as possible. Large stuff tend to make people shy away.
It's better to let people have a choice. And how would C:\Program Files\Zsnes be simpler?
whicker: franpa is grammatically correct, and he still gets ripped on? sweener2001: Grammatically correct this one time? sure. every other time? no. does that give him a right? not really.
Okay then why do we need NSRT and zbattle.net and sources when they are in no way connected directly to zsnes? I call having all that stupider along with unneccessary folders.
AFIAK, Netplay will be restored in a future version. As to NSRT, isn't it obvious? Every time someone posts a bug report, they need the NSRT info.
Wouldn't it be convenient to have NSRT installed so the end user won't have to track it down?
It is better to be silent and thought a fool then to open your mouth and remove all doubt
I am Zophar, Master of Sh*t!
[url=http://archlyn.bravejournal.com]View my blog[/url]
LDAWG, I hope you don't mind competition, because I redone my installer.
So now it includes ZSNESW (of course), NSRT, and the Souce Codes of the Apps, but I didn't add zbattle.net because I couldn't find Souce Code for it.
I'm still working on it so it can include a Set Directory Function and other touches.
Linky - [5.06 MBytes]
EDIT:
Made a update for the new WIP. See my thread.
Over 5mb?! Too big!!! Should be no more than 1.5mb IMO. ZSnes isn't that big anyway when compressed with UPX. But here's some ideas I borrowed from the GIMP project...
1. Create a main ZSnes package with the TXT/DOC Readme and GPL License only and anything else vital to the main core program.
2. Form an optional HTML based side package for the Help files.
3. Create a secondary optional source, debugging, and extras package for NSRT, zBattle.net, etc.
More than 90% of the downloads will be for the core package anyway and nobody wants useless and unneccessary software or files they will never use or have use for.
It should probably install the documentation by default, or just make it part of the required main program entries. That way, when somebody tells somebody to read the netplay.txt or whatever, they don't have to re-download the installer to find it.
That's just my 2 cents.
[i]"It is better to have tried and failed than to have failed to try, but the result's the same." - Mike Dennison[/i]
It should probably install the documentation by default, or just make it part of the required main program entries. That way, when somebody tells somebody to read the netplay.txt or whatever, they don't have to re-download the installer to find it.
That's just my 2 cents.
Um, who's project are you speaking of.
If it's mine then I can make it install hiddenly [shoving it down the HDD's read/write head] if ZSNESw is selected.
Bahamut_ZERO_939 wrote:Over 5mb?! Too big!!! Should be no more than 1.5mb IMO.
Most people have DSL or better and atleast a 40 gig hard drive, why should that be a problem, takes like 10 seconds to download.
I do like the idea of an installer, along with all of the extra options, it will make it look more professional to n00bs who have never tried ZSNES before, and I like the concept of being able to set my save and rom directories.
Bahamut_ZERO_939 wrote:Over 5mb?! Too big!!! Should be no more than 1.5mb IMO.
Most people have DSL or better and atleast a 40 gig hard drive, why should that be a problem, takes like 10 seconds to download.
I do like the idea of an installer, along with all of the extra options, it will make it look more professional to n00bs who have never tried ZSNES before, and I like the concept of being able to set my save and rom directories.
But there are some people still on dial-up. You shouldn't try to kill them.
Try out CCleaner and other free software at Piriform