This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Hi, I've been using Lightspeed with VS2005 successfully for a few months now. Yesterday I installed VS 2008 and thought I would try out the designer for Lightspeed. I noticed it wasn't installed so I went back to the installation msi and re-ran it. I chose "Change" and then added the "Lightspeed Model Designer" to be include in the installation. I then let the installation run but I keep getting an error before it completes saying: "A network error occured while attempting to read from the file : E:\Downloads\LightSpeedExpress[1].msi" The installation then fails. Any ideas? Cheers, Craig |
|
|
I assume drive E is local? If so, I'm not sure what's going on there. From the filename it looks like there are two copies of LightSpeed in the Downloads directory so possibly it is trying to pick up the wrong one. My suggestion would be to uninstall your existing copy of LightSpeed (and, since you've had a failed install that may have left traces, I'd check in Control Panel and Program Files that it is fully uninstalled... just in case) and then reinstall from scratch, possibly from a fresh download. If you still get the problem when doing a "clean" install like this, let us know and we'll investigate further. |
|
|
Just to add to this - often Windows installer does not like having the filename of the msi changed. It may not be the case, but as Ivan alludes, if you have multiple copies and one has been named <name>(2).msi then it could cause strange messages as well. This may not be the issue but it might help diagnose the problem. |
|
|
Yes E is local. Not too sure what the issue was. I had to un-install Lightspeed completely and then do a re-install. This fixed the issue. Thanks, Craig |
|