[Ascii2]

The application does not seem to work correctly using Windows 2000 Professional with Service Pack 4; the clock does not appear. A black figure instead appears where it should be.

[Dilusion]

Great Program!!!

I do have some trouble with it tho I use win200 proffesional sp4 and it does just show a dark figure when there is no skin imported from a windows blinds file. but when a skin is applied for example i applied XPProfessionalvIII it skinned the taskbar prety nicely but it still needs work. The start button was skinned ok and theat was good. but the taskbar kind of resizes itself which i think should be fixed too. Lastly the clock doesnt appear unless i resize the taskbar.

But otherwize good Job!!!


edit: I tried another skin and the skinning worked as good as i wanted it the only major problem still is that the clock cannot be seen unless the takbar is resized.

This post has been edited by Dilusion: 02 August 2007 - 02:57 AM

[Dilusion]

Oh sry O got it working now i just had to delete the regestry folder for tclock2 and customize the setting like no put tray clock fill. Great Program !!!

[Magicbobo]

Unfortunately, I tried the version 0.3 and turn out a failure of skinning

I dont't know whether it is about the skin files or language or others.

whatever Xp or 2000
: (

[WildBill]

Uploaded TClock3 0.3.1 and updated the first post.

[Dilusion]

i can never add halos and stuff to the windows for the close button and maximize and stuff can someone post a sceenshot and show how it can be done. or can it be done?

[Drugwash]

I'm sorry to say that none of the previous issues have been fixed in 0.3.1, apart - maybe - for the resources usage that is not that high now. But it still crashes on exit, systray icons still don't show no matter what kind of fill I choose, but most of all, TClock cannot run when Inspectr is enabled and running - it just freezes all processes including Explorer, and will not work until the system is rebooted.
And if I'm not mistaken, the system menu is not being skinned anymore. But I disabled it anyway.
All this is happening on the same Win98SE system (with some system files upgraded) - Pentium III @ 800MHz, 240 MB RAM, 16MB on-board SiS 630 video.

[WildBill]

Sorry. I haven't done any further testing on Win98. My test laptop is running 2k again. The update was an attempt to fix some crash bugs that pop up when TClock3 starts, that I think were due to race conditions. The fix definitely won't affect resource usage.

[WildBill]

Uploaded TClock3 0.3.2 and updated the first thread post. This has two major bugfixes.

[Dilusion]

great it seems that this version lowered explorer.exe cpu usage but still needs work on at start menu skinning it shows pink shadow on left of list

Attached File(s)

•  Tclock3.png (59.35K)
  Number of downloads: 33

This post has been edited by Dilusion: 18 August 2007 - 02:35 AM

[Drugwash]

So, WildBill, is there a chance for you to test this under a Win98 system? There are a bunch of bugs and glitches, more or less crittical and they're pretty delicate to catch, reproduce and/or describe.

Although you lately fixed some issues under Win2k, the 98 ones are still there, three of which are quite major, namely:
- Explorer crash on exit
- Systray icons missing
- Resource leak/excessive usage

Another disturbing issue is the fact that auto-hide doesn't work at all with TClock3, so any maximized window will be behind the taskbar. Given that I always keep the taskbar at the top, access to min/max/close titlebar buttons is denied.

Recently, while testing 0.3.0-0.3.2, I noticed that simply hovering quicklaunch icons raises CPU usage to 100%.

And one other bug I noticed is that the taskbar height can be resized to a value of zero. I simply disabled the sizebar and played dragging the taskbar to raise and lower its height; at one point I dropped it while it was completely invisible (zero height). It couldn't be restored, neither by reenabling the sizebar, nor by closing TClock3 - a reboot was necessary.

I have to mention that I've installed the '256 color' patched explorer.exe (4.72.3612.1710) - dunno if that has any impact on TClock3's behavior.

The above is just a quick review of the most important issues that are present on my system. Only intended as a feedback. Please keep up the good work and hopefully you'll be able to find and fix the 98 issues.

[WildBill]

Fun with screenshots. Laptop running Win2k SP4...forgive the quality, but there's a 200k limit

Attached File(s)

•  screenshot_1.jpg (27.71K)
  Number of downloads: 35
•  screenshot_2.jpg (27.73K)
  Number of downloads: 22
•  screenshot_3.jpg (27.3K)
  Number of downloads: 16
•  screenshot_4.jpg (28.12K)
  Number of downloads: 17
•  screenshot_5.jpg (28.34K)
  Number of downloads: 18
•  screenshot_6.jpg (28.01K)
  Number of downloads: 17
•  screenshot_7.jpg (27.55K)
  Number of downloads: 32

[marxo]

[off] Please post that screenshot [/off]

[WildBill]

Huh? Please post what screenshot?

[marxo]

Wallpaper... Sorry I am a bit tired...

[WildBill]

I dare not as it's copyrighted...it comes with Windows 2000, in the WINNT\Web\Wallpaper folder

This post has been edited by WildBill: 16 August 2007 - 11:50 PM

[marxo]

Oh... Didn't realize that it is in W2K... Tnx...

[damian666]

Hi wildbill, say, does that skinning of the windows work for you? or is it not working at all?
i cant to seem to get it working you know...

could you please let me know?

damian666

[Drugwash]

Off-topic: WildBill, you may create an account at ImageShack and upload any pictures you like. The size limit per picture is much higher (1024kB, IIRC) and there's no global limit on the number of pictures. They automatically offer thumbnail code for forums.

[WildBill]

damian666, on Aug 17 2007, 02:39 AM, said:

Hi wildbill, say, does that skinning of the windows work for you? or is it not working at all?
i cant to seem to get it working you know...

could you please let me know?

damian666

I've been able to get things like WindowBlinds button halos to work (though not perfectly). Skinning things like window borders isn't implemented. The reason (for now, at least) that TClock3 has to know about border images is because, if you're using WindowBlinds, it has to know where the max/min/close buttons are.