Quote:
Originally Posted by Cyphox
edit: of course i tried (you're talking about starting cr reader from start menu after a forced reset, dont you? if you're talking about testing my "preconfigured" cr, i've only done that twice), still a non-functional cr,
|
So you tried starting cr reader from start menu after forced reset. From what you said afterwards, I take that it did not work. As for your "preconfigured" cr, what exactly is preconfigured. I guess you are using cr3.ini and cr3hist.bmk that you have saved some time ago. Anything else?
Quote:
Originally Posted by Cyphox
and i tried another thing:
i restored my backup, started cr via vlasoftlauncher (the way it works just fine normally) and did a hard reset = damaged config
so the corrupted cfg-file is because of the resets/forced powerdowns i had to do.
|
Did you look at the configuration file (cr3.ini). What did happen? Was it empty? Was the content incomplete? In which way was it corrupted?
Quote:
Originally Posted by Cyphox
but i cant say for sure if cr freezes or if its just the touchscreen/powerswitch that doesnt work after launching cr for the second time directly from start menu.
|
Strange that it works once, but not twice.
Quote:
Originally Posted by Cyphox
maybe im talking nonsense now, but perhaps cr doesnt like the touchpad-driver/plugin that startmenu provides in some way. correct me if im wrong, but when you launch vlasoftlauncher, it doesnt use the driver provided by startmenu but it loads the driver again by itself, doesnt it?!
|
You are right, it does use the drivers/libraries provided by vlasovsoft. In the first update that I uploaded, this was different, since the start menu and vlasovsoft used the same drivers/libraries for some time. But the last version of vlasovsoft uses different drivers/libraries. Therefore I uploaded finally, a new version of the update.