ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

DonationCoder.com Software > T-Clock

T-Clock 2010 (download)

<< < (158/169) > >>

mouser:
Just wanted to say thanks for the update  :up:

nolan_vede:
Hi WhiteTigX.

Ive been using T-Clock Redux v2.4.0 (beta 3, build 384) since Nov 27, 2015.

I just tried v2.4.1#414-beta portable, and this error popped up

T-Clock 2010 (download)

I thought maybe the problem was I needed an executable...that possibly the previous 2.4.0.384 install was an executable, not portable (couldn't remember for sure), but since I could not find an executable anywhere, I downloaded a second T-Clock Redux v2.4.0 (beta 3, build 384) portable today for comparison purposes. 

Testing the second (portable) version of 2.4.0.384 brings up the same error as version 2.4.1.  Also, the Clock64.exe from the original 2.4.0 Ive been successfully using is 235 kb.  The Clock64.exe from the second download of v2.4.0 is only 208kb, although the mouseover from both shows 2.4.0.384

thanks

WhiteTigX:
looks like you didn't download the static version^^
And you've downloaded the old version (since Beta2 is currently only available as a "static" version because AppVeyor somehow failed to pickup my release tag...)

nolan_vede:
looks like you didn't download the static version^^
And you've downloaded the old version (since Beta2 is currently only available as a "static" version because AppVeyor somehow failed to pickup my release tag...)
-WhiteTigX (August 04, 2016, 05:43 PM)
--- End quote ---
Yes.  All good now. Thanks.

T-Clock can be used in a portable way when you create a T-Clock.ini file (either manually or with .reset_portable.cmd)
Or what kind of portable did you mean?-WhiteTigX (July 10, 2016, 05:41 PM)
--- End quote ---
Forgive me, Im a little lost here.  All I did was unzip the files, place them in a folder and run Clock64.exe.  In the previous version I had customizations, but never had an .ini file.  Yet, the new version opens with all my old customizations intact, which is o.k., but I dont know how it happened.  Have they been written to the registry? If so, I'd prefer to have an .ini if possible instead of the registry entries.  Is there a t-clock option I'm missing to create an .ini?  Or, how do I use the .reset_portable.cmd?

WhiteTigX:
you just execute that cmd script :P
But it'll only "activate" the portable mode, it doesn't remove or convert your settings from registry... (yet)

So you'd still have to cleanup the registry yourself, see #16 or #15

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version