[FIXED][Algodoo v.1.7.2 beta] Algodoo won't run.

[tatt61880]

Fixed at v1.7.3
This bug occurred only with v1.7.2.

-Tatt
----



Specs:
1.7.2
O/S: Windows XP SP3
CPU: Intel(R) Pentium(R) D CPU 3.00 GHz
RAM: 1.5 GB
GPU: ATI Radeon X1550

I get an error when trying to run Algodoo:
"The procedure entry point CreateSymbolicLinkW could not be located in the dynamic link library KERNEL32.DLL."
Though it looks like that may be a problem with that registry file.

I also find it odd that it still asks for you to run Algodoo even though you've removed it.

[gradyfitz]

I get an error when trying to run Algodoo:
"The procedure entry point CreateSymbolicLinkW could not be located in the dynamic link library KERNEL32.DLL."
Though it looks like that may be a problem with that registry file.

I also find it odd that it still asks for you to run Algodoo even though you've removed it.

Ah I think that this and
[1.7.2] Installation issue on Windows XP x64
are very closely related, I'll delete that thread and move it here.

This error happened to me because I dropped the .NET framework 3.5 requirement from the launch (I assume).

--
1.7.2
O/S: Windows XP Professional x64 Edition (5.2, Build 3790)
CPU: Phenom II X4
RAM: 8-10GB
GPU: nVidia 9600 GT
--
Using .NET Framework 4.0 x64
Using WIC(enu).
--

.NET Framework 4.0 is not detected by the installer, dropping this launch requirement gets Algodoo installed, but another error then appears.

The error is as follows:
"Algodoo.exe - Entry Point Not Found"
"The procedure entry point CreateSymbolicLinkW could not be located in the dynamic link library KERNEL32.dll"

I discount this error as being a result of dropping the .NET framework requirement, but I thought if it helps provide some insight into the problem it could help.

I'm using the binary from Today, 9 June 2010, 1:55:27 PM (GMT/UTC+10).

Though 1.7.2 doesn't want to install, 1.7.1 seems to run a lot more frames per second when WIC is installed.

I might have had some trouble with .NET framework in the past but I don't remember whether it was resolved.

Is this issue a general x64 issue, a general XP x64 issue, or just an issue with my computer?

---

WIC → wic_x64_enu.exe Wednesday, 25 October 2006, 5:57:45 AM
.NET Framework 4.0 installer → dotNetFx40_Full_setup.exe Friday, 19 March 2010, 1:20:26 PM
→ dotNetFx40_Full_x86_x64.exe Friday, 19 March 2010, 12:44:38 PM

If you need more information, let me know .

EDIT: I just thought I'd mention, in my situation, I'm not able to get into the install itself. I think it would be helpful if you could include your system specs too so we have some kind of common factor more than the error message.

[Versieon]

I have this problem to, i think it is the NET. framework as i think it was just updated...

System Info
Microsoft Windows XP Service Pack 3

Dell Vostro
Intel Core 2 Quad CPU @ 2.40GHz
2.39GHz, 2.00 GB of Ram
ATI Radeon HD 3400 Series

[Joel]

Thank you, we believe to have identified the problem and are working on a fix for it.

[RicH]

Thanks. I hope it gets fixed soon.

[emilk]

This should be fixed in 1.7.3: http://www.algodoo.com/download/Algodoo_1_7_3-Win32.exe