|
Pages: [1]
|
 |
|
Author
|
Topic: Force installer to use local files? (Read 3664 times)
|
lhouk
Zebranky food
 Offline
Posts: 5
|
I'm having problems installing uqm 0.4. I've downloaded both uqm-0.4.0-win32-installer.exe and uqm-0.4.0-content.uqm, and I put them both in the same directory (C:\TEMP). On a Win2K system, when I run the installer, I get a DOS command box, and it "goes to sleep". On a WinXP system, when I run it, I also get a DOS command box, and the cursor starts bouncing all around inside the command box, as it too "goes to sleep". In neither case does the install ever do anything else, and I have to kill the DOS box.
Since I have the content file in the same directory, is there a command option to the installer that will force it to skip trying to access the network and immediately use the local file? Something like "-local" or "/no_network"? Or is there just something I am doing wrong? Thanks in advance to all who respond!
|
|
|
|
|
Logged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
lhouk
Zebranky food
Offline
Posts: 5
|
Yes, it's doable, and quite easy. Put the files somewhere, like this: bla\uqm.exe bla\content\version bla\content\packages\uqm-0.4.0-content.uqm bla\content\packages\uqm-0.4.0-~update-20060114.0000.zip The .exe file would be a snapshot from the most recent development version, which you could get from http://uqm.stack.nl/files/snapshots. As it's newer, and the content has changed, the extra uqm content update file is needed. You can get it from the same page.
I downloaded the current .exe and content update file, set up the directory structure following your example, crossed my fingers, and ran uqm.exe. I got the following error message:
The application has failed to start because SDL.dll was not found. Re-installing the application may fix this problem.
Since I couldn't reinstall, I did a quick Google search. I found and downloaded SDL.dll, and moved it to the same directory as uqm.exe. I ran uqm.exe again, and got a new error message:
The procedure entry point SDL_Has3DNow could not be located in the dynamic link library SDL.dll.
I suspect I don't have the most recent SDL.dll, but I tried downloading it from three or four different sites, all with the same result. Can I impose on you once more to point me to a link for a working SDL.dll (or tell me what I am doing wrong)? And by the way, thanks again for your help and patience with me.
|
|
|
|
|
Logged
|
|
|
|
|
|
lhouk
Zebranky food
Offline
Posts: 5
|
From the INSTALL file:
...
Those sites should probably have the neccessary runtime libraries for you. If not, I could send you mine (i forget exactly where I got them).
Thanks, Halleck! I followed your instructions, and it works flawlessly. My top-level directory now contains:
Volume in drive D is Local Disk
Volume Serial Number is A4C1-D11C
Directory of D:\programs\uqm
02/01/2006 03:33 PM <DIR> .
02/01/2006 03:33 PM <DIR> ..
01/31/2006 11:31 AM <DIR> content
02/01/2006 03:11 PM <DIR> include
04/05/2001 06:24 PM 169,443 jpeg.dll
02/01/2006 03:11 PM <DIR> lib
04/05/2001 06:24 PM 94,720 libpng1.dll
07/19/2002 07:34 AM 49,152 ogg.dll
02/01/2006 03:10 PM <DIR> oggvorbis-win32sdk-1.0
08/28/2005 01:07 AM 237,568 SDL.dll
04/05/2001 06:24 PM 18,944 SDL_image.dll
02/01/2006 03:33 PM 103,699 stderr.txt
01/14/2006 12:06 AM 3,203,267 uqm.exe
07/19/2002 07:34 AM 974,848 vorbis.dll
07/19/2002 07:35 AM 28,672 vorbisfile.dll
04/05/2001 06:24 PM 53,760 zlib.dll
07/20/2005 11:48 AM 59,904 zlib1.dll
11 File(s) 4,993,977 bytes
6 Dir(s) 7,625,588,736 bytes free
and it wasn't enough just to have the .DLLs, in case anyone else reads this in the future. I also had to have the various subdirectories, which were created when I unzipped the various .ZIP files into my top-level directory.
Again, a big thank you to both Halleck and Meep-Eep for their kind and patient assistance!
Leslie
|
|
|
|
|
Logged
|
|
|
|
Michael Martin
Core Team
*Smell* controller
Offline
Posts: 387
|
It does sound like NSIS itself wasn't running properly on lhouk's system.
For the record, the following claims should be true for both the 0.4 and new 0.5 installers:
- It explicitly asks (right after asking for the install directory) from where it should read local packages. It will only attempt to download a file if it needs it, it's not in the package directory, and it's not already installed.
- The package directory defaults to the directory the installer EXE is in, which is not necessarily the same as the working directory. If it isn't, that's a bug in NSIS. (Windows Explorer has been mentioned, but unless it behaves differently when you go through "My Computer", the defaults are presented correctly from it on my machine. NSIS also has different variables for referring to the working directory and the executable's directory.)
- No external package is touched or checked until you've fully configured your install and committed to begin the process, so if you don't get to that point, it's not the external packages' fault.
|
|
|
|
|
Logged
|
|
|
|
|
Pages: [1]
|
|
|
|
|
