LAST EDITED ON Sep-13-01 AT 09:53 PM (EST)This is an outline of my method of packaging a route for distribution. This is not the one and only correct way to do it, just the method I'm currently using. Some of the steps, references, and methods will have to be adjusted for things that are unique to your route. This is not a dummies guide with step by step and pictures, I'm assuming anyone who has a route ready for distribution is computer savvy enough to understand what I'm talking about. I'm not even going to copy this to my old claris works to run the spelLcHekkkuRr on it, cuz if I hti the wrong \*.*key you'll figure it out if you're smarte enuff.Using PortOgdenV31 as an example, here's what I did.
First, I deleted the \envfiles, \shapes, \sound, \terrtex, and \textures folders.
Second, I did a tools, find, files or folders named *.BK *E.RAW *N.RAW , select all and hit the delete key. You can do one file type at a time, but if you put a space between each and watch the syntax you can do all three at once. The .BK are backup files generated by the route editor and are unnecessary if there are no problems with the route, and if you're getting error messages you need to fix those anyway first. The files in the \Tiles directory that end with E.RAW and *N.RAW are for lighting and geometry, and according to the newest FAQ (first time I ever got any useful information out of a MS faq) these are automatically regenerated the first time the sim is run when they're not there, and I tried it, works flawlessly first time every time. Port Ogden version 3 was 1.8 megs zipped up, and I added a few kilobytes rather than subtracting any and also bulked it up with the self extraction feature, but the elimination of the *E.RAW and *N.RAW files shrunk the zip down to 1.02 megs for 3.1.
Next I added a new folder named \custom, and pasted in my coal.ace texture for the coalmine. I then pasted in a copy of EZSTUFF2.BAT, edited it to copy the custom texture into the \terrtex and terrtex\snow, and saved it as INSTALV3.BAT. Then I zipped it up, deleted the portogdenv31 folder from the \routes directory, and tested both the extraction and the install bat a few times before making the self extractor.
That's pretty much it, the EZSTUFF2.BAT I used for a template is available in the utilities section of the file library in GITSTUFD.ZIP, but there are several things you should know about it. First, I have Windows 98SE, and I have heard that the /Y switch should be added for WIN2000XP to eliminate the need to answer the overwrite prompt, because it processes DOS commands differently, and I've also heard rumors that some future operating systems are not going to support DOS commands at all. Second, I wrote it for COMBOREF, and it needs to have CALL XCOPY ..\..\GLOBAL and the assorted shapes and textures folders added in order to work with ALL_OBJECTS.REF for the editor. I also wrote it from a rusty wetware memory bank, and I've since dug up my old DOS 5 manual from the attic, and found it would be a lot less cumbersome if I had remembered the /S switch at the end of the command line, which eliminates the need for the duplicate command lines to get the subdirectories. Third, it copies files with the same name over each other, so if you cut and paste a set of references under each other it changes the kind of textures you get. For example, as is you will get the USA2 track textures since they are in the last set that overwrites the previous. Look at V3.1's instalV3.bat, and you will see why I have european track textures in the route. Some people are running their batch files from the root of \routes rather than self contained in the root of the add on, if you want to do it that way you need to change the shortcut convention for XCOPY. DOS has a problem returning a "too many parameters" error when it hits the spaces in those long file names, and the workaround uses ".\" which is "within this directory", and the double dot backslash, go up one directory, double dot backslash double dot backslash, go up two directories, etc. So if you are going to run the batch somewhere else other than inside your route's folder, you will need to alter those. For an example, take a look at SETUP.BAT for the new Danish route, which uses a version of EZSTUFF2 modified to work from the \routes directory. Again, understand that this is what worked for me, other possibilities are out there, try a few and see what you like best. I tried a couple of the other utilities for route developers, some of them I can't get to work, and another one, altho it makes some spectacular promises, strikes me as being too cumbersome and complicated for the end user to get the route working after the download. Maybe you'll have better luck.
There are also setup.exe makers, freeware and shareware, available from zdnet and other places which would do away with the need for these clunky batch files altogether, but I'm a slow learner so it's going to take me quite a while to figure out how to use them.
The one thing I did figure out how to use was Winzip self extractor 2.2, which unlike the dumbed down version that comes with the regular version, includes the ability to add a command line to run a setup.exe or install batch file automatically after the extraction is finished. So that's what I used for the auto install, just typed in the name of my batch file in the appropriate box. Demo version of that is available at www.winzip.com .
Pack 'em up boys, I got a 40gig hard disk just CRYING for as many different routes as I can pack on it.Jim "Sniper" Ward
On the Island of Sodor
Printer-friendly page | Top
Route distribution packaging - the zipper guide. [View All], sniper297, 09:46 PM, Sep-13-01, (0) RE: Route distribution packaging - the zipper guide., TheEagle, Sep-14-01, 02:17 AM, (1) RE: Route distribution packaging - the zipper guide., sniper297, Sep-14-01, 03:06 AM, (2) RE: Route distribution packaging - the zipper guide., rgarber, Sep-14-01, 08:43 AM, (3) RE: Route distribution packaging - the zipper guide., TheEagle, Sep-14-01, 09:36 AM, (4) RE: Route distribution packaging - the zipper guide., sniper297, Sep-14-01, 08:09 PM, (5) RE: Route distribution packaging - the zipper guide., TheEagle, Sep-15-01, 04:00 PM, (6) RE: Route distribution packaging - the zipper guide., GandyDancer, Sep-15-01, 06:47 PM, (7) RE: Route distribution packaging - the zipper guide., sniper297, Sep-15-01, 07:03 PM, (8) RE: Route distribution packaging - the zipper guide., GandyDancer, Sep-15-01, 07:27 PM, (9)
Conferences | Topics | Previous Topic | Next Topic
TheEagle
Charter Member
Sep-14-01, 02:17 AM (EST)
1. "RE: Route distribution packaging - the zipper guide."
In response to message #0
First of all, I made my own bat file and the only problem why I didn't work at many people is because they didn't have a 'template' folder into their MSTS directory. I mean, the template folder was created when you installed MSTS wasn't it?Secondly, what's the difference between the command 'Xcopy' and 'Call Xcopy' ?Third of all, you mentioned that a /y switch should be added to elimante those 'overwrite prompts' in win 2000 xp but I don't see that command into your bat file (the Bat file from your Portogden route).
Printer-friendly page | Top