Train-Sim.Com
MSTS Activity Design

Activity unpackaging error: "Expected more files"?

Notice to all visitors and members of the Train-Sim.Com message forums:
If you plan on using a signature banner in your posts, we would like to remind you that there is a maximum size for banners. That maximum is 450 pixels wide by 120 pixels high, and not to exceed 25k. Your compliance is appreciated. FORUM RULES Problems? There are two common reasons for problems with logging in and posting messages. The first is that you are running a firewall that prevents your messages from being sent to the server. The other is that you have cookies disabled; the DCForum software requires cookies to work properly.

Previous Topic | Next Topic

Printer-friendly copy Email this topic to a friend

Reading Topic #1429

Charter Member · 261 posts

Is anyone familiar with what causes this message to appear and how it is overcome?The new Activity which I uploaded yesterday, for the San Diego & Arizona route, is throwing this message up and causing nervous irritations and gastric ulcers to my expectant public! (A solution would, I suppose, be just to zip all the appropriate files but that would be defeating the purpose of the packager!)Bruce.

AustRail

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

RE: Activity unpackaging error: "Expected more files"??, downside, Jan-23-03, 01:41 PM, (1) RE: Activity unpackaging error: "Expected more files"??, kevarc, Jan-23-03, 02:08 PM, (2) RE: Activity unpackaging error: "Expected more files"??, kmanc21, Jan-23-03, 07:45 PM, (3) RE: Activity unpackaging error: "Expected more files"??, brucek, Jan-23-03, 10:58 PM, (4) RE: Activity unpackaging error: "Expected more files"??, elementb, Jan-25-03, 07:50 AM, (5) RE: Activity unpackaging error:, elementb, Jan-25-03, 08:08 AM, (6) RE: Activity unpackaging error:, dvdhoven, Jan-25-03, 10:19 AM, (7)

Conferences | Topics | Previous Topic | Next Topic

Charter Member · 1318 posts

RE: Activity unpackaging error: "Expected more files"??

Several people seem to have come across this recently and I haven't seen a cogent answer on the subject.Why not put it into a self installer - in any case some people (me included) like to see what everything is rather than just chuck it into the folders. I have my own way of dealing with packagers (provided they work in the first place ).Hope you get it sorted.Bill

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 3086 posts

RE: Activity unpackaging error: "Expected more files"??

Some routes for some unknown reason just don't like the packager. It only includes the act file and not the rest. What you can do in explorer is create a folder with the needed subfolder, put the files in them and then zip it up. BTW, don't forget the consists.Kevin Arceneaux
It is time for Amtrak to become a fallen flag!Activity unpackaging error: "Expected more files"??? – image 1

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 178 posts

RE: Activity unpackaging error: "Expected more files"??

The author uploaded a new version of the activity with all the necessary files. I'm running the activity now without problemsKen

How did I survive before MSTS

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 261 posts

RE: Activity unpackaging error: "Expected more files"??

Phew! It's good to read that, Ken! I discovered the reason for the packager spitting the dummy: it won't accept file names outside the bounds of DOS conventions, i.e, no more than 8 characters in the prefix (followed by the three-character suffix, of course!)This makes using unique names very difficult but it's something which I shall bear in mind for future efforts.Bruce.

AustRail

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 2 posts

RE: Activity unpackaging error: "Expected more files"??

The reason that this error happens is that the route directory name is different then the track database name. In the case of the San Diego route the directory name is SDA20 I believe but the track database is SDA1. If you change the route directory to SDA1 then you should be able to package the activity correctly. You will also find this problem with the East Metro route and any route that is installed within route control. This only effects the packaging of the activity, from what I have seen the name of the route directory does not matter when you are installing the acivity as it will look for the name in the track database.We discovered this problem when trying to package activities for these routes at www.vnerr.com.Hope this helps.Brian Element
mow@nverr.com

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 2 posts

RE: Activity unpackaging error:

The reason that this error happens is that the route directory name is different then the track database name. In the case of the San Diego route the directory name is SDA20 I believe but the track database is SDA1. If you change the route directory to SDA1 then you should be able to package the activity correctly. You will also find this problem with the East Metro route and any route that is installed within route control. This only effects the packaging of the activity, from what I have seen the name of the route directory does not matter when you are installing the acivity as it will look for the name in the track database.We discovered this problem when trying to package activities for these routes at www.vnerr.com.Hope this helps.Brian Element
North Eastern Railroad
mow@nverr.com

Alert | IP

Printer-friendly page | Edit | Reply | Reply With Quote | Top

Charter Member · 1732 posts

RE: Activity unpackaging error:

Hi,Thanks Brian, for clearing this up. Never to old to learn. Dick van den HovenActivity unpackaging error: "Expected more files"??? – image 2

Alert | IP


[ Home | MSTS Forum | MSTS FAQ | File Library ] Copyright © 2002 by Nels Anderson. All Rights Reserved.

Restored from the Train-Sim.Com archive, captured January 9, 2005. About this archive.