May 21, Puiu. Windows 11 review round-up: Better than Windows 10, but still a work in progress. Replies 29 Views 3K. Oct 10, PenguinJoe. Replies 39 Views 5K. Dec 16, Amet Jassil. Latest posts. Intel Celeron G can match iK's single-threaded performance Crinkles replied 24 minutes ago. Install this update to resolve an issue where the JScript version 5.
Install this update to resolve an issue where the private data of the DEVMODE data structure may be corrupted on a bit version of Windows when using a bit application in raw mode to print a document. Install this update to resolve an issue where a third-party driver installed on a computer that is running Windows XP may prevent you from opening files successfully on a NTFS file system volume. Install this update to resolve an issue where you receive a 0xf Stop error after installing security update KB MS Install this update to address an issue where the TZ environment variable may not work as expected due to Daylight Savings Time changes in the United States.
Install this update to resolve an issue in which you receive a stop 0x1a or stop 0x0a error message on a computer running Windows XP Service Pack 2. This update fixes false error messages that occur when the latency of Internet connections causes problems while adding time. Installing this update enables your computer to automatically adjust the computer clock on the correct date in due to revised Daylight Saving Time laws in many countries.
Install this update to fix a situation where your Windows-based system that supports processor power management features, and is equipped with multiple processors, may experience decreased performance. Install this update to resolve timing issues resulting in race conditions when using Bluetooth devices connected via USB. This update resolves a performance issue with the Phishing Filter. When visiting certain web pages, the Phishing Filter may increase CPU usage while evaluating the page contents and the system may become slow to respond.
This problem occurs on pages that contain multiple frames or when multiple frame navigations occur quickly. Install this update to address an issue where a Windows XP-based portable computer may not have as long a battery life under certain circumstances when certain USB 2.
You can use USMT to perform unattended migrations and to migrate files and settings for computers with multiple users. Also, with USMT you have the ability to encrypt and compress the store. USMT 3. This tool includes two command-line tools named ScanState and LoadState. ScanState creates an intermediate store that contains the user files and settings from the source computer.
LoadState restores these files and settings to the destination computer. You can alter the default. Depending on what you want to migrate, you can specify all or none of the default. The entire migration process is controlled by the.
When using USMT for automated migration, in almost all cases, you should modify the migration. Install this update to resolve an issue in which after you apply security update KB MS , programs unexpectedly stop during initialization without providing any error messages.
When visiting a Web page that uses a custom pop-up object, Microsoft Internet Explorer 6 can close unexpectedly and generate an error in the Mshtml. A problem has been identified in Filter Manager that can prevent you from installing updates from Windows update.
You can help protect your computer by installing this update from Microsoft. The Network Diagnostics for Windows XP tool analyzes information about your network connectivity to help you troubleshoot network-related problems with your computer.
Install this update to prevent an issue in which you may receive a "Stop 0xD" error message on a computer that is running Windows XP Service Pack 2. The error may occur during startup, or after the system has started. Install this update to fix a situation where you cannot create a network connection when you are starting a Windows XP SP2-based computer. During boot time, the hard-coded firewall boot policy blocks traffic on the default UDP port until the firewall service is running.
Install this update to enable your computer to automatically adjust the computer clock on the correct date. Install this update to resolve an issue in which you receive a "stop 0x7e in aec. SYS is the acoustic echo canceling driver. The Microsoft Windows Server Scalable Networking Pack contains functionality for offloading network processing to hardware. A service to help with slow log off and unreconciled profile caused by profile hive unload problems. Symptoms of these problems include events in the application event log with source Userenv and event id where the message text indicates a profile unload problem and the error is "Access is denied" or event id or The service is set to automatically start when the computer boots so you will not need to start it manually.
Version 1. NET Framework is required. If you download the full setup package, this software will be automatically installed if it is not already present on your system. Please see the companion whitepaper or the readme file for complete details. Install this update to prevent or resolve an issue in which Windows Update and Automatic Updates can no longer download updates after an Access Violation error occurs when using the Automatic Updates service.
Install this update to resolve an issue in which you cannot view the contents of a subfolder on a network share. Install this update on Windows XP Service Pack 1 systems to resolve an issue where System Restore may not work correctly or certain services may not function properly after using System Restore on SP1.
Using it, you can install and uninstall color profiles, change color profile associations for displays, printers and scanners, view detailed properties for color profiles including a 3D rendering of the color space gamut , and rename color profiles, keeping the filenames and "internal" names consistent. This tool also enables Windows to automatically adjust the gamut curve of the display when a color profile containing gamut table information is set as the default profile for the display.
Typically, such profiles are created by custom monitor calibration tools, such as those available from ColorVision, GretagMacbeth, and X-Rite. NET Framework 1. The Tools tab will allow further diagnostic tools to be launched from within the System Configuration Utility. Security issues have been identified that could allow an attacker to compromise a computer running Internet Explorer and gain control over it. This update installs a permanent copy of Package Installer for Windows to enable software updates to have a significantly smaller download size.
The Package Installer facilitates the install of software updates for Microsoft Windows operating systems and other Microsoft products. This update resolves an issue with Windows-based systems that may prevent other software updates from installing properly. It also resolves an issue that may reduce the maximum displayable screen resolution. This issue only affects machines using one of the following languages: Brazilian Portuguese, Indonesian, Hindi, Malay, or Thai.
This update addresses an issue in which messages are improperly handled if the subject line contains the word "begin" and a display issue concerning watched threads in newsgroups. This update also addresses two issues in which Outlook Express stops responding. When you work in a program that loads both version 5 and version 6 of the Comctl Note: You may also see mixed window styles when you experience this problem.
If a program selects Comctl If you navigate to:. I found the following recommendations from one web page that mentions this utility:. For people who want to navigate the Java version of the utility instead on a Mac, there is a useful walkthrough of the same procedure available at:. It does cover using the Windows utility, but their installation procedure is more complicated than the one I outline. By the way: you point to a firmware upgrade utility for LaCie drives in your April 7, notes.
Note that LaCie uses a totally different storage format for the upgrade so the data files aren't interchangeable. It appears that every vendor supplying new firmware for Oxford based devices is using the V3. If the updater utility correctly identifies your chipset and current running version, it should be safe to update. Your concern about compatibility certainly is warranted, as there are plenty of sites giving out bad versions i. This end-user contacted us again a few days later saying that the Oxford Semiconductor delayed write failure was now fixed since he updated the chip firmware.
He does, however, appear to have power management issues in the Maxtor drive itself. In case this information is useful, we wanted to post it as well. He goes on to say:. One final comment on this whole mess. After leaving the drive connected but unused for a few hours, it never came back again properly and I had the old delayed write failure again. There are lots of reports of issues with Maxtor drives connected with Firewire doing this: a good set is at.
So it appears that as long as I keep the drive doing something occasionally while it's connected, it's fine. But if the drive ever is unused for long enough that it starts sleeping, it won't come out of that properly and should be disconnected before being used again.
I can live with that. Windows XP Service Pack 2 is now released and we have some initial test results to share with you. We produced a test application that showed the delayed write failure always. Although an initial release candidate of Service Pack 2 didn't work around it, we are happy to report that the released version of Service Pack 2 does indeed solve the problem for us. If you are running Windows XP, and if you are experiencing any delayed write failures, you should see if Service Pack 2 improves the situation for you.
If it doesn't, some of the solutions cited above may work for you. While I have your attention, I have another gripe. I have not retested this with Service Pack 2 so I do not know if this problem is solved or not. The problem is this. I have my bus powered drive on my system and it's working fine. I then attach another drive. It could be a DVD recorder or whatever.
When I hot plug the device into my controller not to my hard drive , my hard drive completely shuts down. The overall system gets unstable. This has happened to me several times now. It's probably related to an earlier problem I cited where I couldn't stream from my DV camera to my ATA hard drive when a drive was on the controller as well. Whose fault is it? Is it the OS? The drive?
The controller? I don't know but I have been very frustrated with all the stability problems I have had with Personally, I'm going to try and just use my card for a DV camera and nothing else. Your mileage, of course, may vary. This update can fix the delayed write failure if your case uses this chip. Another end-user has written to us letting us know that Microsoft has had an XP patch available for some time on their WEB site.
In reading through their site, this could be the fix for the problem we've seen where hot plugging a drive shuts down the bus. I do not know if this patch addresses any delayed write failures. However, if you do not want to upgrade to Service Pack 2 for whatever reason , you can still download this one individual patch. You can download the patch from here. Given the severity of the problem, it's unfortunate this patch wasn't made available through a more obvious means, such as the Windows updater.
Could have saved me a few headaches I have received a number of e-mails from end-users letting me know that this site has helped them resolve their delayed write failure problems. Thank you for taking the time to keep us updated. As for my own hard drive status, things are going reasonably well. I do have one remaining problem. Once in a while, and it is not always reproducible, my hard drive locks up when the system resumes.
I can sometimes get it out of this state by unplugging it and plugging it back in. Usually it results in an unstable system and a reboot is required. Fortunately this doesn't happen very often.
I don't have enough time to try and diagnose who is at fault with this issue so I'll just live with it. The "delayed write failure" is gone for me with Service Pack 2, but I still keep my little filter driver installed as a secondary safety check. I figure it served me well for well over a year; why tempt fate? I disabled UDMA5 and set the maximum transfer to with the utility.
But if I try to set the max transfer to the message error is back. So with the maximum transfer set to and Udma5 disabled my external drive is now stable. The error never come back but my system was very slow.
It's very important to test a lot of settings to resolve the problem. Surfed, experimented, and eventually found solution: in the Setup, disable PCI bus power management. The majority of problems end-users have reported to us seems to stem from this K bridge chip limitation described in detail above. There are many other causes, unfortunately.
We continue to get an occasional e-mail with yet more solutions. Here are some recent reports. Although Windows XP Service Pack 2 is a solution to the delayed write failure for some users, for other users, we are getting reports that SP2 generates more delayed write failures.
If this is your case, a workaround to your problem is likely above. First try our delayed write test application and see if it fails at sectors backup your hard drive first!!! If it fails at sectors, you have the K bridge chip limitation; workarounds are cited above. We receive quite a few e-mails from end-users telling us that they found a solution above to their delayed write failure. Here is one such e-mail with a slight twist to a resolution found above.
Perhaps it might help others:. I found your doc at www. I have included details here as it may help someone else. The guts of the solution that worked for me is the same as that posted under the entry for 26 May 04 but there are some differences which may be useful to note.
This web page receives a considerable amount of traffic each day. It would seem that the delayed write failure with drives is still pervasive. Most end-users we have communicated with have found a resolution to their delayed write failures above. However, we still occasionally receive e-mails with new twists and solutions. Here are two interesting e-mails we have received from end-users who wanted to share their story. Hi, I'm another victim of the delayed write error, but not anymore.
If you don't mind, I'll tell you all of what happened, in hopes it will help someone else. I moved to XP SP2, and sure enough, I started to get delayed write errors under odd circumstances--usually, when some program or another went to save a file, but not under normal file transfers. So I tried flashing the firmware. I came across three different versions of Oxford's flash utility, the latest of which does not allow modification of the all-important settings, block size and DMA.
But it brought up an interesting point--that the firmware uploader seems to be very touchy, and should only be run by itself. Anyways, in that process, I ended up performing an incomplete write to the flash memory. Luckily, the uploader that comes from ByteCC, for the F, turned out to be the most useful of them all--in the directory "FW9", there is a command-line program to reset the flash memory to receive for its initial firmware in the factory.
Had to use that, and I was back to square one. So once I had a grasp of the whole process, I first tried the old, original firmware, from At block size, at UDMA4, the drive worked correctly. Then I flashed to the most recent firmware. At block size, at UDMA5, it worked just right. I plugged that into my firewire card, right next to my external enclosure. These crippled my system a couple times, because I turned on the camera while in Avid XPress Pro I'm a film student , and the program kept trying to write to the external drive.
Of course, with delayed write failures of that magnitude, it damages all the directories on the drive, often to the point where the drive has to be reformatted completely. The solution to this connectivity problem is hinted at in documents on firewire, and in Microsoft's knowledge base, but in my opinion, this should be a disclaimer in the manual for ANYTHING firewire:.
I had NO idea this was true, and I've never even heard it mentioned among anyone else with a firewire setup. Maybe I'm sheltered. But when I plugged the camera and drive into my card on two seperate ports, the drive was slowing down to mbps, the speed of the camera, and hence, the delayed writes.
So I established a chain Not only did this work, but detection of all components was faster and more reliable. Funny thing is, this has never been an issue on Macs, from what I've seen. So I'm pretty sure it's an issue with the Windows XP not understanding the varying speeds in a less-than-perfect firewire setup.
Service Pack 2 only makes the problem worse. I hope this information proves useful, and I apologize for the lengthy message. I'm just surprised how rare your site is in having information on this phenomenon. Without it, I probably wouldn't have come to the conclusions I did to fix my own problems. I came to your site from the Dell forum regarding the delayed write problem documented there some time ago.
I'm not sure whether the issue is still 'alive,' so to speak, but if so I would like to add my 2 cents worth. With your Test utility the problem was reproducible every time I ran it, sometimes getting to around 45 percent through, sometimes only 15 percent. This made no difference whatsoever, but given that it wasn't specifically for the delay write problem, I am not surprised.
I also played around with various Virtual Memory settings as that seems to have been an area where some have found success. I had little initial success until I settled on Mb for the initial size and Mb for the maximum size. That's double my physical RAM Mb for min and quadruple for max. I just ran your Test utility three times consecutively without an error being reported. I'm keeping my fingers crossed. Some might think that my Virtual memory settings are extreme, but I normally use different min and max values of about half the size I reported that now appears to work.
I hope this assists your cataloguing of information on this problem. Thanks for your good work. Thanks to Andrew, we have been made aware of a Microsoft update to XP Service Pack 2 that apparently fixes some issues, including delayed write failures. The Microsoft site states:. After you install Windows XP Service Pack 2, some devices such as digital cameras that use S speed may not perform as expected.
Install this update to help prevent this issue. After you install this update, you will have to restart your computer. Click here for full details. The disk inside is a Western Digital one. I tried your tester, and it happily wrote all the sectors, so that told me a little more, but not much. The Firewire card is one provided by Pinnacle with Pinnacle Studio 8, is certified on Microsoft's hardware compatibility web site and works fine with my Minolta scanner, although it had failed to communicate properly with my wife's Mini I-Pod.
This should have been a clue, but I had forgotten this. The LaCie troubleshooting utility from their web site recognised the drive OK and it passed all the tests there, including extracting the internal disc information. Bingo, drive behaved perfectly, and I threw a MB file at it which it accepted in no time with no errors at all.
So it appears to be the card: I checked and the drivers for the IEEE hardware are identical on both computers. I have since written about 20 GB to the disc from the laptop with no error at all. So it looks like I need a better quality IEEE card, and not to rely on Microsoft certification to tell me that it will actually work! By the way, I did try two different 6 pin to 6 pin cables between PC and external; didn't make any difference.
Got to your web site from googleing "delayed write error". This is what I finally discovered while debugging:. I then put the oxford DVDRW at the end of the chain and populated the drives and your test runs to completion no error. This test was run using a 64bit PPA controller.
Only the speed was used since my boxes are only. However, I am only guessing as to what that old oxford enclosure was using. Maybe it was only using pio mode. Is there a way to tell? Joseph has e-mailed us again to let us know that he received a patch from Microsoft for Windows XP Service Pack 2 that fixes his hard drive problems. Microsoft has a KB article that details this. The symptoms are:. For example, you may receive an error message, or the computer may stop responding. The specific symptom may depend on the software that you use in conjunction with the IEEE device.
This problem does not occur if you have more than one IEEE device connected, and then you disconnect a device. I am not sure if I am contacting the right department. I did want to share this information. You will find it at:. I have run your Bustrace Test several times with "no" errors. I could not do this with earlier Prolific firmware versions. I had my share of "delayed write" failures, corrupted files and unreadable hard drives with previous firmware releases. I was about to give up using my external cases for anything but DVD writers until I found this V version.
I have done file compare to Original and copied back to original drive all with no errors. I would hope those who use this new firmware release will have similar results.
I would like to credit "showarthing" for sharing this release. Thanks for posting this. Thank you so much for your help! I am a bit compulsive so have been up searching since about 8 hours ago. When I found your site, complete with warnings of drive falure from your test, I backed up 20 gigs or so onto DVDs, and ran the latest firmware update November's with the latest ROM installer 2.
After the ROM update, the test completed in about a minute, with no errors. Thank you so much! Will writes us with another link from Microsoft that can resolve some failures, including delayed write failures.
We have received several more "success" stories on resolving delayed write failures. Gerald writes us:. Very useful test program Now I can run your test program. I just wanted to share my experience with delayed write failures on an external USB 2. Lacie tech support could not help me and I was ready to scrap the drive.
It had already corrupted about gigabytes of music that I had ripped from my music collection. Every friggin' song had CRC failures; in fact, I think the actual quality of the song was degraded. Many of my songs had pops and skips. Anyway, after reading the log that bustrace has on delayed write failures, i decided to first increase my virtual memory to 1. This did not work. Then I began to read about the Oxford bridge problem. So, I dismantled my lacie drive.
Sure enough, the bridge was made by Oxford. So, I downloaded the Macally files that another reader used to update the k bridge problem. But, like the log said, it was very cryptic but from what I discovered, there is an "uploader" program that updated the bridge firmware. But, you need to connect the drive via firewire, not USB. Luckily for Lacie drive owners, Lacie publishes an updater. But the information on the updater does not say that it is used to fix the Oxford adapter used in all their drives.
But that is its sole purpose. Once I updated the Lacie drive using the firmware, the stress test program has worked beautifully and I am ready to begin transferring files back on the drive that I was ready to toss.
I solved my delay write failed issue in windows SP4. They made my card which has the Agere FW chipset. They took me through a bunch of steps but eventually it just came down to that little piece of software. Michael writes us to let us know that he did not have the K problem we cite above, and our test program worked without any issues. Still, he would receive delayed write failures. The solutions cited above did not work for him either.
He ended up resolving his problem by updating the Windows drivers from Unibrain using their ubCore 3. Fabian writes us to let us know that a firmware upgrade for his Prolific bridge chip fixed his and USB failures:. My drive bought in december was from "Chiligreen" lousily assembled, tighten all the screws before use! First crash after a few days after running for some hours it suddenly said "Could not write Mft Same thing several times - I went crazy.
By the way: Ontrack Easy Recovery is a great utility, it recovers most of the things within a few hours. I updated with the November firmware and the 2. I saved the old firmware, but could not figure out which version it was. Anyway, thanks a lot to all the guys for the information! Rick writes us with an interesting story that we wanted to pass on.
I used it with the firewire connection flawlessly on a friends MSI Mega barebone, but as soon as I connected it to my own Shuttle SN45G which uses the Realtek chipset, within 15 minutes the drive was totally ruined.
Chkdsk says "unable to determine NTFS version info". The test. I downloaded and flashed using the latest Prolific firmware which had no effect. I'm running Windows with SP4. Thanks for the excellent web page on this very frustrating problem. I applied the Maxtor patch referenced above, and the Microsoft patch also, but saw no difference. Maxtor suggested the same, so I bought a new card and bingo--no more Delayed Write Failures.
It took a week of futzing around, but the problem is gone, thanks in large part to your site! So I patched my firmware and it worked fine.
I was trying to allow support for 2 IDE devices master and slave when I Anyway my newer Sarotech devices were all using the Prolific chipset which allows support for CDROMs and hard disks which I patched with the November firmware and they are also working perfect now.
Furthermore my cousin's Ranger Hardbox, which is identical to the Sarotech Hardbox, was using a PL, which was also successfully patched. Thank you for keeping the information forum on the delayed write failures DWF. After the firmware update, DWF were not observed for three weeks:. However, delayed write failures would still occur if the drive was daisy-chained as a second device on the firewire bus, and the first device malfunctioned.
Operation of this drive as a USB 2. I have a EZQuest drive with an Oxford chip. I finally hit this page, the firmwire updating did the trick. My drive is well and sound now. I have a Plumax enclosure with a PL rev. C chip. Your super helpful test program fails at the or sector transfer varies. I flashed it to the latest firmware, In desperation I applied the MaxK device filter referenced on your page.
Sure enough, this works -- the test program passes! But the hitch is that the transfers are now limited to such small chunks that it takes seconds -- 3x slower than USB!
0コメント