Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Pastimes : Computer Learning -- Ignore unavailable to you. Want to Upgrade?

To: Bill Fischofer who wrote (25109)	1/30/2002 5:29:36 PM
From: Eric L	Read Replies (1) \| Respond to of 110655

Bill, << I'm very familiar with PCSync 3.0 since I use the same program. >> In my case, I'm using the new "XP" drivers for the old translucent purple USB cable for v 1.0 as opposed to the newer "gold" cable. << Yes, bad device drivers are the root of most ills on XP >> Or bad drivers (us users) who don't install them correctly, or misinterpret the install instructions, or the authors of the instructions, or a combination of the above. In my case, I misinterpreted the (somewhat poor) instructions from Laplink's tech bulletin on troubleshooting the USB link, which eventually led to the failure to boot on my new system after installing them. Even after I got everything installed correctly, both my systems seem to be a tad unstable when the USB network bridge driver is active, and I'm not convinced the "safely remove hardware" function really "safely" removes them. Before a PCsynch session I always set a system restore point, and as soon as I'm finished with a session I "safely remove hardware" then disconnect the cable, and set another system restore point. ... but it is a fine program. I would generally recommend it to anyone migrating systems or doing Laplink type file transfers or synchronization ... and the USB connection beats the old serial cables by a ton, but I'll be more comfortable when certified and signed drivers are available. << which is why eventually everyone will be forced to provide digitally signed and XP-certified drivers. My guess is it will take another year or so before all the hardware folks get their act together. >> It will ... and there is probably a big queue right now. Writing certifiable drivers, or certifying them is tedious. I have had the pleasure to work with the Redmond NT driver guys face to face on a few occasions. I have great respect for them. << Fortunately XP provides a pretty sophisticated system restore point and driver rollback scheme which can avoid most problems. >> The System Restore function is super. A GREAT feature of XP. I keep a shortcut to it on my desktop right beside the Computer Management shortcut. Having said that ... the "failure to boot" I described above occurred because after failing to get the USB driverI restored my system to a day old restore point, and when I attempted to restart a windows/system32 file was clobbered and in need of repair and I was too inexperienced with XP Pro (and so was the Dell tech I had on the phone) at that time, to repair it. Next time around, I'll probably be able to. I guess my point is that the System Restore function, and the inherent stability of XP can make a user a little too cocky, particularly since the elimination of DOS (finally rid of those !@#$%^& HEAPS) makes recovery a tad more difficult with XP than its WIN 3.xx, Win 95 xx, WIN 98, predecessors, even with ASR and a fine backup procedure. Best, - Eric -