Free Allegiance Forums

When it's autoupdating, it tries to rewrite a file, then fails and asks if I want to retry...I retry, and it fails again.

Tried with a clean install, didn't help.

I'm running Windows 7. Will post specs and system info as soon as I have time (school is calling).

Have you tried "run as administrator"?

For me it sound like you use an old installer. You can download the latest one from http://getsetup.alleg.net.

Tried the new installer, ran everything I could as an administrator, and got the same message:

Code 183: cannot create a file when that file already exists.

Source: Autoupdate\filelist.txt
Dest: \filelist.txt

Do you wish to retry moving the files?

~~~

It confuses me. I ran it just fine before the update

My comp is a laptop. Here's my system info:

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.110622-1506)
System Manufacturer: Hewlett-Packard
System Model: HP Pavilion dv7 Notebook PC
BIOS: Default System BIOS
Processor: Intel® Core™ i5 CPU M 450 @ 2.40GHz (4 CPUs), ~2.4GHz
Memory: 4096MB RAM
Available OS Memory: 3894MB RAM
Page File: 3435MB used, 4350MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode

The video cards are an ATI Mobility Radeon 5470 (primary) and an Intel Integrated Graphics (crap). It has that switchable graphics feature for more battery life.

Make a copy of filelist.txt then try to delete the original. If it doesn't delete, you may have malware or something that locked it down.

It deleted just fine. Hmmm...

Funji wrote:QUOTE (Funji @ Nov 20 2011, 02:39 AM) Code 183: cannot create a file when that file already exists.

That error appears, if the program doesn't have write permission on file system.

Weird. It installed previous updates just fine. Would reinstalling in a different place help? (I'm testing this now actually)

Test finished. It updated and launched properly when I DIDN'T install it in the C drive. Should have known, heh.