Ian Nicholls

Ian Nicholls

Joined Member # 219018
0 Posts 0 Replies 388 Reputation

Ever since version 2 of the launchpad appeared in early August, I have been unable to update it from version 1. I get as far as agreeing to download the list of files but it refuses to download one particular file and times out after three tries. The log file reads as follows:-- [Installing] ----------------------------------------------------- Server: http://sdcentral2.stardock.com Server Dir: public Network Id: odnt Name: Object Desktop Launchpad App Id: lp

3 Replies 2,227 Views

Ever since version 2 of the launchpad appeared in early August, I have been unable to update it from version 1. I get as far as agreeing to download the list of files but it refuses to download one particular file and times out after three tries. The log file reads as follows:-- [Installing] ----------------------------------------------------- Server: http://sdcentral2.stardock.com Server Dir: public Netw

0 Replies 1,654 Views

Neil I can't speak about Copernic Agent Basic, but the version of C A Personal that I have the problem with is also version 6.12 build 722. As far as I know the Basic version has the same panes. Have you tried contacting Copernic.com themselves? They may well allow you access to the Personal or Professional versions for a trial period. <img src="http://images.stardock.com/wc/icons/wc.gif"

4 Replies 3,482 Views

Even with the latest version of Windowblinds, the three left-hand panes in the main Copernic window still have a black background, making text and buttons impossible to see: they are "Quick Search", "Common Tasks" and "Page Preview". Is there any hope of resolving this other than to prevent Copernic being skinned? Ian

4 Replies 3,482 Views

I should like to add my experience to that of #20 by lbolton. I too have a black panel on the left hand side of the screen with Copernic Agent Personal. It should have coloured text on a white backgorund. The only way to deal with this is to exclude it from being skinned. The problem has not been resolved with any of the WB5 releases to date. Best wishes Ian <img src="http://im

43 Replies 20,322 Views

Since updating to the latest WB beta - 4.90d[b].002 I have had the same problem twice. Whilst loading for the first time after the computer is switched on, Windows halts and the machine re-boots, causing Windows to perform a disk check as it re-starts. In each case, it detects a couple of errors in the files on Drive C, but different errors each time. The WB trouble-shooting report is as follows:- WindowBlinds 5 BETA Troubleshooting Repor

2 Replies 2,582 Views

I am using version 4.90d[b].002. Copernic skinned properly with Windowblinds version 4. Would screen prints of the application showing the problem and one with Copernic left unskinned be helpful? If so, how do I include them? Best wishes Ian

4 Replies 2,843 Views

Sorry, my problem was being stuck with the classic desktop! However, the next version of the beta has cured that. There is another problem with the latest beta, which I have just reported to you. It concerns Copernic Agent Personal. If I have not given enough detail please let me know. I can always send you a screen capture so you can see what's going on. Best wishes Ian

3 Replies 3,062 Views

The latest beta of Windowblinds 5 is not skinning Copernic Agent Personal properly. The panes on the left-hand side of the main search window are rendered in black until a search has been carried out. Even then only part of the panes changes to the correct black text on a white background. Also parts of the background are rendered as transparent when they should be white. This problem occurs with Copernic version 6.12, build 722. I am running Wind

4 Replies 2,843 Views

I did what everyone else has done. My troubleshooting message reads:- WindowBlinds 5 BETA Troubleshooting Report: WindowBlinds is installed correctly on this PC. Your machine supports per pixel borders on WindowBlinds skins. If you suffer visible corruption (overbright) on the frames and have a NVIDIA board then please be aware this is a NVIDIA bug. It has been seen on GeForce 4 cards and some FX seri

3 Replies 3,062 Views