Open GoogleCodeExporter opened 8 years ago
Sorry. I cannot reproduce the problem this time.
Original comment by crendk...@gmail.com
on 25 Aug 2010 at 1:30
What if you extract the installer and install manually with the batch scripts?
Original comment by crendk...@gmail.com
on 25 Aug 2010 at 1:31
On my system i see the following in the eventlog (W7 x64 - SP1 beta):
Application popup: Microsoft Visual C++ Runtime Library : Runtime Error!
Program: C:\Program Files (x86)\gdipp\gdipp_svc_64.exe
R6030
- CRT not initialized
Original comment by mmihe...@gmail.com
on 25 Aug 2010 at 6:52
I saw one user complaining that when using registry mode the demo programs will
fail with the same error. I am using registry loading as well since I found no
other way to make the 0.8.2/0.9.0 version to work on W7U x64 SP1-beta.
I removed the AppLoad entries and the services can now start without the
runtime error!
Original comment by mmihe...@gmail.com
on 25 Aug 2010 at 7:04
I saw one user complaining that when using registry mode the demo programs will
fail with the same error. I am using registry loading as well since I found no
other way to make the 0.8.2/0.9.0 version to work on W7U x64 SP1-beta.
I removed the AppLoad entries and the services can now start without the
runtime error!
Original comment by mmihe...@gmail.com
on 25 Aug 2010 at 7:04
I don't know if it's an installation problem ... because I can successfully
install the program, even if I have to ignore the advertisment that the service
cannot start.
Original comment by netca...@gmail.com
on 25 Aug 2010 at 7:06
where are located these AppLoad entries?
After msi extraction ... what am I suppose to launch to start the installation?
Original comment by netca...@gmail.com
on 25 Aug 2010 at 7:22
The "CRT not intialized" error is actually one of the errors supposed to be
fixed in 0.9.0. How can you still produce that? Please provide detailed steps.
You can find what registry is modified in the README document. After you
extract the files, go to the "Script" directory and run the script files. If
you need service load mode, run "Create_Services.bat" and
"Start_Service_xx.bat". If you need registry load mode, run
"Registry_Enable_32.bat" in case you have 32-bit Windows, or
"Registry_Enable_64.bat" in case you have 64-bit Windows.
Original comment by crendk...@gmail.com
on 26 Aug 2010 at 2:52
shouldn't I install something before create and start the service?
Original comment by netca...@gmail.com
on 26 Aug 2010 at 6:05
It is recommended to install with installer. If you cannot use the service load
mode, choose loader mode, and then use the scripts.
Original comment by crendk...@gmail.com
on 27 Aug 2010 at 8:06
The problem is that I can install with installer ... but there's no way to
start the service!
Original comment by netca...@gmail.com
on 27 Aug 2010 at 8:37
You should be able to start the services used the BAT files in the script
directory - use "Run as Administrator" otherwise it wont work.
Original comment by ankan.ba...@gmail.com
on 29 Apr 2011 at 7:31
Original issue reported on code.google.com by
netca...@gmail.com
on 24 Aug 2010 at 9:57