Cixert

Yes, you're right. I should have said that those were the MBR limits and not w2000-XP-w2003. It is already corrected. Thank you

It should be simple, but I can't seem to get it right. Unlike newer Windows versions, XP does not preserve folder dates with copy and paste. Objective: Copy all files and folders from one partition data to another from XP, preserving the folder date. The new partition has a different file system and a new cluster size, so clones aren't possible. It's possible to make a copy to an image and then unzip it, but that seems like a long time to copy 1 TiB and a lot of free space is required. I've seen several programs that copy files and folders while preserving the folder's backup date, but these programs don't copy to the root directory; they only copy to a single folder. Therefore, they wouldn't be suitable for maintaining a well-organized file allocation table and could cause problems with long filenames. These are: -Argentum Backup -Cobian Backup -Fbackup So, I decided to look for a program that copies files and folders to the root directory. I've tried over 20 programs, and it doesn't seem to exist. By example these do not retain the date: -Carifreed SimplySync Backup -Microsoft Richcopy -Microsoft Robocopy (command line) I've only gotten a little bit of success with XXclone (command line), but only halfway. It turns out that using /T only copies folders, not files. So I'd have to copy the folders first with xxcopy Q:\ K:\ /E /H /K /T And then the files with xxcopy Q:\ K:\ /E /H /K (Q: and K: are the drive letters) Are there commands in xxclone to copy one partition to another while preserving the folder's date? Is there a program with a graphical interface that can do this? I don't think I'm asking for anything special. I don't understand why it's so difficult... Edit: Achieved with Total Commander. You must first select "Copy date/time from directories" in the settings menu + copy/delete. Any other programs?

I have checked and verified the maximum size limits for FAT32, exFAT, and NTFS partitions based on the cluster size. Physical tests were performed using MiniTool Partition Wizard 10.3 on both Windows XP and Windows 10. Some tests have also been performed using Eassos Disk Genius. The hard drives used were Seagate 5 Tb / 6 Tb / 8 Tb and WD 10 Tb. In FAT 32, the calculation is real. In exFAT, I was able to simulate limits of 256 TiB. In NTFS, the calculation is real up to 10 Tb. MAXIMUM LIMITS BY FILE SYSTEM FAT32 File System Maximum FAT32 partition size in MBR --> 8 TiB Maximum FAT32 cluster size in MBR --> 512 KiB Maximum FAT32 partition size in GPT --> 2 TiB Maximum FAT32 cluster size in GPT --> 64 KiB exFAT File System Maximum exFAT partition size --> 256 TiB Maximum exFAT cluster size --> 32768 KiB NTFS File System Maximum NTFS partition size --> 255.99 TiB Maximum NTFS cluster size --> 512 KiB MAXIMUM LIMITS BY PARTITIONING SCHEME MBR Partitioning Scheme* Maximum MBR size on hard disk with 512 byte logical sectors --> 1.99 TiB Maximum MBR size on hard disk with 4096 byte logical sectors --> 15.99 TiB *The limits for the maximum MBR size with logical sector 512 bytes and logical sector 4096 bytes is this real calculation: 1.9999999995343387126922607421875 TiB 15.9999999962747097015380859375 TiB GPT Partitioning Scheme Maximum GPT size on hard disk with 512 byte logical sectors --> 8 ZiB Maximum GPT size on hard disk with 4096 byte logical sectors --> 65536 ZiB 2^64 sectors × 512 bytes = 8 ZiB 2^64 sectors × 4096 bytes = 65536 ZiB *The actual GPT limit is determined by the real limit of file systems which is much lower. MAXIMUM LIMITS BY CLUSTER SIZE FAT32 Partition Limit Cluster 4 KiB = 0.29 TiB / 300.99 GiB / 308223.99 MiB Cluster 8 KiB = 0.59 TiB / 601.99 GiB / 616447.99 MiB Cluster 16 KiB = 1.17 TiB / 1203.99 GiB / 1232895.99 MiB* Cluster 32 KiB = 2.35 TiB / 2407.99 GiB / 2465791.99 MiB Cluster 64 KiB = 4.70 TiB / 4815.99 GiB / 4931583.99 MiB Cluster 128 KiB = 8.00 TiB / 8192.00 GiB / 8388607,50 MiB Cluster 128 KiB = 9.40 TiB / 9631.99 GiB / 9863157.76 MiB Cluster 256 KiB = 18.81 TiB / 19263.99 GiB / 19726325.76 MiB (FAT32 real limit 8 TiB in MBR and 2 TiB in GPT) *Just I exceeds only 3.4 GiB the limit for cluster 16 KiB and problems arose. exFAT Partition Limits Cluster 0.5 KiB = 0.12 TiB / 129.00 GiB / 132104.05 MiB Cluster 1 KiB = 0.25 TiB / 257.00 GiB / 263172.00 MiB Cluster 2 KiB = 0.50 TiB / 513.00 GiB / 525313.97 MiB Cluster 4 KiB = 1.00 TiB / 1025.00 GiB / 1049600.95 MiB Cluster 8 KiB = 2.00 TiB / 2049.00 GiB / 2098176.40 MiB Cluster 16 KiB = 4.00 TiB / 4097.00 GiB / 4195328.06 MiB Cluster 32 KiB = 8.00 TiB / 8192.99 GiB / 8389631.74 MiB Cluster 64 KiB = 16.00 TiB / 16384.99 GiB / 16778239.30 MiB Cluster 128 KiB = 32.00 TiB / 32768.99 GiB / 33555454.52 MiB Cluster 256 KiB = 64.00 TiB / 65536.99 GiB / 67109885.01 MiB Cluster 512 KiB = 128.00 TiB / 131072.00 GiB / 134218746.00 MiB Cluster 1024 KiB = 256.00 TiB / 262144.00 GiB / 268435456.00 MiB ...and so on to cluster 32768 KiB (32 MiB) = 8192 TiB (exFAT real limit 256 TiB) NTFS Partition Limits* Cluster 0.5 KiB = 1.99 TiB / 2047.99 GiB / 2097151.99 MiB Cluster 1 KiB = 3.99 TiB / 4095.99 GiB / 4194303.99 MiB Cluster 2 KiB = 7.99 TiB / 8191.99 GiB / 8388607.99 MiB Cluster 4 KiB = 15.99 TiB / 16384.99 GiB / 16777215.99 MiB Cluster 8 KiB = 31.99 TiB / 32767.99 GiB / 33554431.99 MiB Cluster 16 KiB = 63.99 TiB / 65535.99 GiB / 67108863.98 MiB Cluster 32 KiB = 127.99 TiB / 131071.99 GiB / 134217727.96 MiB Cluster 64 KiB = 255.99 TiB / 262143.99 GiB / 268435455.93 MiB Cluster 128 KiB = 511.99 TiB / 524287.99 GiB / 536870911.87 MiB Cluster 256 KiB = 1023.99 TiB / 1048575.99 GiB / 1073741823.75 MiB ...and so on to cluster 32768 KiB (32 MiB) = 131040.00 TiB (NTFS real limit 255,99 TiB) *Values from cluster 4/8/16/32/64 have been calculated by the previous amounts and I have not verified their correct operation. I think the calculation is 2^32 -1 cluster. The NTFS file system is limited to 32 bits, so the above limits cannot be exceeded under any circumstances. https://learn.microsoft.com/es-es/windows-server/storage/file-server/ntfs-overview In theory, the difference between MBR and GPT is that GPT is capable of redirecting 64 bytes physical sectors. Therefore, with GPT, is it possible to exceed 2 TiB on a hard disk with 512 bytes physical sectors by formatting with a 4 KiB cluster size, and exceed 16 TiB on a disk with 4096 bytes physical sectors by formatting with a 8 KiB cluster size?* *I haven't verified this last point. Let's see if a user with disks larger than 16 TB can confirm if partitions larger than 15.99 TiB are possible.

I purchased a 10Tb Western Digital My Elements 25A3 (external USB drive), and the "WD Quick Formatter" software transformed the drive's logical sector from 512 bytes to 4096 bytes, so it works in Windows XP in MBR mode with 10 Tb. I had one issue: Both WD Quick Formatter 1.2.0.10 and WD Quick Formatter 2.0.0.65 ran in Windows XP, but they failed to complete the format, displaying the message "error: the format could not be completed." (No options appeared in XP, but I assume the attempt was in XP mode.) Then I ran WD Quick Formatter 2.0.0.65 in both Windows Seven and Windows 10, and the options "format in XP mode" and "format in Vista mode" appeared. (It wasn't necessary to run it on Windows 10 LTSB 2015 in Windows Seven compatibility mode for the option to appear, as some users report for Windows 10) I selected XP mode, and the disk was successfully formatted into a single 10Tb partition in MBR mode with a 4096 bytes logical sector. I then booted into Windows XP and divided the disk into multiple partitions using Eassos Disk Genius DiskGenius 5.6.0.1565.

Supposedly, it's the boot partition. Although it is created on both boot and data disks. It also serves to save the decryption of encrypted partitions, so this partition cannot be encrypted. Before using any disk initialized by the manufacturer or by Windows that created that partition, what I do is erase the entire disk and create new partitions with Eassos Disk Genius. In both NT 5.x and NT 6-10, I create my own boot partition formatted in FAT32. (The misnamed version 11 doesn't seem to support it in FAT32.) In NT 6-10, the partition I created appears hidden without a letter. So I assign it the letter B so I can access it. If I recall correctly, Windows NT 6-10 can also be booted without that partition. And of course, this can be removed from data disks if these don't have encrypted partitions.

Thanks, adding "--make-default-browser" to the Supermium shortcut doesn't start it. I tried "--make default browser" without the hyphens, and it does start. Neither method immediately set Supermium as the default browser. However, when I restarted Windows XP, Supermium appeared as the default browser. So, I don't know which method was used to set the default browser. From what I am investigating you must also manually assign the HTM and HTML extensions to be open with Supermium. But this will not work if the command "--make-default-browser" is not added to direct access, before or after assigning extensions.

Let's see if I understand this correctly... I'm looking for a USB 3.0 card for Windows 2000 Vanilla. According to the Japanese page I read with the translator, I seem to understand that the cards with the chips ASMedia 1041, ASMedia 1042, Texas Instruments TUSB7340 and Texas Instruments TUSB7320 are compatible with Windows 2000 Vanilla, by example in this cards: -RocketU 1144a --> driver RocketU 1.12.9.0 (ASMedia ASM1042U) --> I can't find this card in Europe. -Planex PL-US3IF04PE --> chip Texas Instruments TUSB7340 --> I only see this card in Japan. -Oriented Interface Card SATA3 USB3.0 0 Combo Card SATA3 + USB3.0 0 – PCIe --> Asmedia Driver V1.16.1.0 mod ---> I only see this card in Japan. Please @blackwingcat the driver link is down https://w2k.flxsrv.org/cgi-bin/dl.cgi?file=asm1.16.1.0w2k.zip - Silverstone SST-EC04 --> This card I see in Europe but I see that it has chip NEC uPD720201 and I read in the same publication that NEC is not compatible with Windows 2000. Any other cards available in Europe? Edit: The driver is in waybackmachine https://web.archive.org/web/20190503123742/https://w2k.flxsrv.org/cgi-bin/dl.cgi?file=asm1.16.1.0w2k.zip

Does anyone know how to make Supermium the default browser in XP? Supermium's help says that it cannot be set as the default browser. I have tried to manually assign the htm and html extensions to open by default in Supermium, but despite selecting it in the XP menu Tools+Folder Options instead of opening with Supermium they open with XPchrome. I choose the Supermium path in file types and a message appears saying that Chromium will be the default application. It turns out that Chromium is XPchrome without having chosen it.

Well, it's March 11, 2025 and XPchrome browser 115.0.5790.136 is still working. No time bombs have gone off. I found the browser in general to be very good, faster and with fewer bugs than Supermium at the time. Now Supermium has evolved while no new version of XPchrome has been released. I think the criticisms made about XPchrome are excessive. We XP users are not in a position to make demands. If the author wants to sell the browser commercially, that seems fine to me. Unfortunately, I don't see the project continuing at this time.

After 15 days recovering data from the two hard disks that I did Cut-Paste on. Today I connected the new broken Toshiba disk to a third USB adapter, in another house, with another computer and it worked perfectly. I don't understand it although it seems very good to me. Has it been repaired from resting these days? Until I get the data out I'm not going to try it on the other computer with the other 2 adapters.

The power adapter has a label that says: 12v 2000A. These are the same values that the label of other USB adapters says. I have tested the power cable with a tester, it gives 14.6v and 3600A. I think these are normal values, although there are 4 things to consider: 1- All testers measure about 2v too much in all power adapters. I don't know why this is, thinking it could be a fault of my tester I went to the store and tried a more expensive one, the result is the same. 2- When I try to measure the amps it shows 3.6 A at first and then the value disappears from the screen in less than 1 second. I don't know if this is normal. 3- In the eBay ad where I bought the USB adapter it says that the power adapter is not very strong so you shouldn't use the device for permanent connection, just for a while. I don't know what the seller means by this. It either works or it doesn't work and I don't see it getting hot. 4- The USB adapter seems to work regardless of whether the power adapter is connected. I haven't done a definitive test but the files seem to copy to any hard drive just the same. In other USB adapters when I disconnect the power adapter the hard drive disconnects from the computer. Anyway, even if it were a problem with the power adapter, I don't see the connection between this and a mechanical failure of the hard drive.

Thanks, it's strange and it's not the first time this has happened to me. The other time I blamed the latest versions 11 and 12 of Minitool Partition Wizard, I don't remember exactly why, but these versions don't work well. Maybe once the partitions were created I formatted them with this one. I don't know, what seems clear is that I created them with DiskGenius since they start in sector 256 and Minitool starts them in sector 2048. If there is any news I will comment. And if anyone knows how Disk Manager deletes partitions just by starting the service, please comment.

Thanks for the help. Finally the culprit was LC Technology - PhotoRecovery When scanning a 3 TB MBR hard drive with logical sector 4096 bytes the program is not able to retain the location of the files found and generates an error copying each file to a temporary location in the .prpro.scratch folder. Once Windows/temp is full it starts filling the first existing partition and once it is full the next one. This is not a justifiable behavior and I don't know how Windows security allows this behavior without user intervention. LC Technology - PhotoRecovery generates a log file with the errors and the behavior, here is an extract: [Devices::Win32::DeviceManagerImpl::rescanDevices] this=[DeviceManagerImpl:]: J:\\ 02:05:18.504 (debug) (T:7828) DeviceManagerImpl.cpp:315 [Devices::Win32::DeviceManagerImpl::rescanDevices] this=[DeviceManagerImpl:]: PD:USBSTOR\\DISK&VEN_TOSHIBA&PROD_EXTERNAL_USB&REV_0\\20221206018168F&0 02:05:18.507 (debug) (T:7828) DeviceManagerImpl.cpp:310 [Devices::Win32::DeviceManagerImpl::rescanDevices] this=[DeviceManagerImpl:]: LD:STORAGE\\VOLUME\\{98433D34-E44C-11EF-9D97-90FBA64B5AC7}#000001635F83B800 02:05:18.510 (debug) (T:7828) DeviceManagerImpl.cpp:312 [Devices::Win32::DeviceManagerImpl::rescanDevices] this=[DeviceManagerImpl:]: K:\\ 02:05:18.512 (debug) (T:7828) DeviceManagerImpl.cpp:315 [Devices::Win32::DeviceManagerImpl::rescanDevices] this=[DeviceManagerImpl:]: PD:USBSTOR\\DISK&VEN_TOSHIBA&PROD_EXTERNAL_USB&REV_0\\20221206018168F&0 02:05:18.514 (debug) (T:7828) DeviceManagerImpl.cpp:318 [Devices::Win32::DeviceManagerImpl::rescanDevices] this=[DeviceManagerImpl:]: ==END LOGICAL DEVICE MAP== 02:05:18.525 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: Z:\\ 02:05:18.528 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: Z: \[2,E\]=Z: 02:05:18.531 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: B:\\ 02:05:18.534 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: B: \[2,E\]=B: 02:05:18.538 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: C:\\ 02:05:18.541 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: C: \[1,E\]=C: 02:05:18.543 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: D:\\ 02:05:18.545 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: D: \[2,E\]=D: 02:05:18.547 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: E:\\ 02:05:18.549 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: E: \[2,E\]=E: 02:05:18.552 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: F:\\ 02:05:18.555 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: F: \[2,E\]=F: 02:05:18.558 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: I:\\ 02:05:18.561 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: I: \[2,E\]=I: 02:05:18.563 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: J:\\ 02:05:18.565 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: J: \[2,E\]=J: 02:05:18.567 (debug) (T:7828) WorkDirectories.cpp:337 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: MP 0: K:\\ 02:05:18.569 (debug) (T:7828) WorkDirectories.cpp:359 [PRApp::WorkDirectories::initVolumeList] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:0)]]: K: \[2,E\]=K: 02:05:18.573 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:9) [Volume: Root=B: WorkDir=B: Enabled=1 Priority=2] [Volume: Root=C: WorkDir=C: Enabled=1 Priority=1] [Volume: Root=D: WorkDir=D: Enabled=1 Priority=2] [Volume: Root=E: WorkDir=E: Enabled=1 Priority=2] [Volume: Root=F: WorkDir=F: Enabled=1 Priority=2]]]: B: \[2,E\]=B: 02:05:18.576 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:9) [Volume: Root=B: WorkDir=B: Enabled=1 Priority=2] [Volume: Root=C: WorkDir=C: Enabled=1 Priority=1] [Volume: Root=D: WorkDir=D: Enabled=1 Priority=2] [Volume: Root=E: WorkDir=E: Enabled=1 Priority=2] [Volume: Root=F: WorkDir=F: Enabled=1 Priority=2]]]: C: \[1,E\]=C: 02:05:18.579 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:9) [Volume: Root=B: WorkDir=B: Enabled=1 Priority=2] [Volume: Root=C: WorkDir=C: Enabled=1 Priority=1] [Volume: Root=D: WorkDir=D: Enabled=1 Priority=2] [Volume: Root=E: WorkDir=E: Enabled=1 Priority=2] [Volume: Root=F: WorkDir=F: Enabled=1 Priority=2]]]: D: \[2,E\]=D: 02:05:18.583 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:9) [Volume: Root=B: WorkDir=B: Enabled=1 Priority=2] [Volume: Root=C: WorkDir=C: Enabled=1 Priority=1] [Volume: Root=D: WorkDir=D: Enabled=1 Priority=2] [Volume: Root=E: WorkDir=E: Enabled=1 Priority=2] [Volume: Root=F: WorkDir=F: Enabled=1 Priority=2]]]: E: \[2,E\]=E: 02:05:18.585 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:9) [Volume: Root=B: WorkDir=B: Enabled=1 Priority=2] [Volume: Root=C: WorkDir=C: Enabled=1 Priority=1] [Volume: Root=D: WorkDir=D: Enabled=1 Priority=2] [Volume: Root=E: WorkDir=E: Enabled=1 Priority=2] [Volume: Root=F: WorkDir=F: Enabled=1 Priority=2]]]: F: \[2,E\]=F: 02:05:18.587 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:9) [Volume: Root=B: WorkDir=B: Enabled=1 Priority=2] [Volume: Root=C: WorkDir=C: Enabled=1 Priority=1] [Volume: Root=D: WorkDir=D: Enabled=1 Priority=2] [Volume: Root=E: WorkDir=E: Enabled=1 Priority=2] [Volume: Root=F: WorkDir=F: Enabled=1 Priority=2]]]: I: \[2,E\]=I: 02:05:18.589 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=[WorkDirectories: ScratchDir=.prpro.scratch Volumes=[(list:9) [Volume: Root=B: WorkDir=B: Enabled=1 Priority=2] [Volume: Root=C: WorkDir=C: Enabled=1 Priority=1] [Volume: Root=D: WorkDir=D: Enabled=1 Priority=2] [Volume: Root=E: WorkDir=E: Enabled=1 Priority=2] [Volume: Root=F: WorkDir=F: Enabled=1 Priority=2]]]: J: \[2,E\]=J: 02:05:18.591 (debug) (T:7828) WorkDirectories.cpp:371 [PRApp::WorkDirectories::rebuildVolumeByPriority] this=

In C:\Windows\Temp I don't see any programs running, but I do see the following folders: \Crashpad -metadata -settings.dat \MsEdgeCrashpad -metadata -settings.dat -throttle_store.dat But these are old folders and files, 2024 February. At this point I have been able to delete all the folders ".prpro.scratch" except the one located at: C:\Users\user_name\AppData\Local\Temp I deleted the files inside and they were recreated immediately afterwards. Also created: -MicrosoftEdgeUpdate.log

It has happened again. My suspicion is that it is a file recovery program, since the recovery drive is the only one that is not filled with these files. This time Renee Undeleter and Ontrack Easy Recovery are closed. So only the following are left open: -EaseUS data Recovery. -iBoysoftDataRecovery. -LC Photorecovery Professional. -Piriform Recuva. Is possible to see in some Windows 10 log who creates these files? In System Events I only see several errors related to the Microsoft Edge update. -EventData 0 crashpad_log No disponible 0 MicrosoftEdgeUpdate.exe 1.3.195.43 InstallError 0x80040902 \\?\C:\ProgramData\Microsoft\EdgeUpdate\Log\MicrosoftEdgeUpdate.log \\?\C:\Windows\TEMP\msedge_installer.log 0 f4b12a7c-ecc8-11ef-9d9c-90fba64b5ac7 262144

No, I didn't know this one

Thanks for the contribution. I had previously posted this error with MBR partitions, but I can't find the post right now. On the 6TB GPT disk connected directly to SATA I created the first partition FAT32 1 GiB cluster 32 KiB aligned to sector 256 with Disk Genius on Windows Seven and then it disappeared just by entering Windows Disk Manager on XP. Now I have created more partitions and the error continues to occur. I will try with another initial sector size when I can empty the disk. If you can do the test with sector 256 and FAT32 cluster 32 KiB I would appreciate it.

I am running several data recovery applications that take several hours to run. When I get to the computer I see that "Renee Undeleter" warns about scratching and I also see the Windows 10 warning "no disk space". I look at the disk drives and see that 8 are full except the attack drive to recover files. All except the system drive contain a folder called ".prpro.scratch" with several GiB in size. Inside there are hundreds of files without extension and all start with the letters PR like: PR0A732D157825533C PR0D2C74353D4D524C PR0D5D2C05570B0007 They measure between 50 KiB and 1.5 GiB. The system drive is also full, but in this case the folder has been created at the path: C:\Users\username\AppData\Local\Temp\.prpro.scratch with tens of GiB. What could be causing this behavior? Other programs I have running are EaseUS Data Recovery, iBoysoftDataRecovery, LC Photorecovery, Piriform Recuva and Ontrack Easy Recovery none of them cause any errors.

Thanks, can you tell me the exact model so I can take a look? Although I'm afraid that these boxes won't allow me to work in Windows 2000/XP with +2TiB disks as Western Digital boxes do, up to 16 Tb, by moving the logical sector from 512 bytes to 4096 bytes.

I have found a new problem working with GPT in Windows XP. Nothing serious if we take the appropriate precautions and also have Windows Vista updated or higher. I found it strange, since the error has not happened to me before. Right now I have the 6 Tb GPT hard disk to which I have only made a 1 TiB partition and left the rest of the space empty. When I open the Windows XP Disk Manager the partition disappears immediately, without performing any additional operation. To prevent losing the partitions I suggest making a partition table copy with Eassos DiskGenius from Windows Seven or higher in the menu Disk>Backup Partition Table. If you do not have a partition table copy, you can recover it with this same program from the menu Tools>Search for Partitions , choosing the Whole Disk option and in the search, clicking on "Reserve" when the appropriate partitions appear. If you know of another suitable program to make a partition table copy, please comment. The pity is that we need Windows Vista or higher or use a bootable CD with a program, since once the partitions are lost in XP the hard disk only shows a capacity of 1493 Gb, so we need to boot an operating system that recognizes the real disk capacity. Maybe it is possible from XP with DMDE, but I don't do it.

Yes, thanks. I bought this hard disk a few months ago and I hadn't used it yet. I hope that the new Western Digital drives are reliable as you say, since in the past I have found otherwise. I'm going to try. Indeed according to BackBlaze, the most reliable is HGST and Western Digital. Although they also list a Seagate drive that has not yet any breakdown. https://www.backblaze.com/cloud-storage/resources/hard-drive-test-data

Of course it is under warranty, but I assume I won't just send them the disk and they will return it to me with the recovered data, right? From what I'm reading from Backblaze's analysis the AFR error rate has increased in recent years across the board for the set of hard drives.

Second hard disk broken this month. This time it's a brand new 2.5" model, a Toshiba PC L200 with 2Tb capacity. After 5 hours of pasting files onto this hard disk via USB 2.0 bridge it started making a clack clack clack sound, which seems like a physical failure. I had the bad idea of cut and paste information onto this drive to use it temporarily as a data drive when I had another drive full. Why doesn't the control Z button work? Another mistake I made was risking using NTFS with a 4KiB cluster for multimedia files. I don't like NTFS, at the beginning of the century I had several Seagate drives broken due to the redundant use of NTFS in the same sectors of the hard drive in the master file table (MFT). Surely sooner or later the drive would have broken anyway, luckily it broke after 5 hours of use with 105GB of information and not later with 2Tb. Is it possible that both drives had mechanical failures due to using the same USB adapter? New with JMicron JMS578 chip which I don't trust to work. https://www.amazon.es/7xinbox-Adaptador-Pulgadas-Compatible-alimentación/dp/B08Y1VQV3Q/ref=asc_df_B08Y1VQV3Q I would like not to argue too much about how bad, awful the Toshiba PC L200 hard disk is. 70 years making hard drives and we still don't know how to do it? Any computer component can be broken, but not the hard drive, please that not! I would like to focus on recovering the data, because this time I have lost 105 GiB (and thank goodness). The two hard disks from which I have extracted them I have not touched. Shouldn't it be easy to recover the data? Over the years I have tried almost all data recovery applications and you know what, I don't like any of them. The attack disk measures 3 Tb with a single FAT32 partition and 32 KiB cluster. A full hard drive scan, as most programs insist, takes several days via USB. I'm currently trying with programs that don't require scanning, such as DMDE, IsoBuster, PC Inspector, Photorescue (Testdisk), and the result is that many files are recovered corrupted. Why can't I recover recently deleted files in another way? How can I physically recover the new damaged hard disk? Several companies offer to do this. Where can I find information on the process? Moral: You have to spend a lot of money to have many hard disks to make backups and never cut and paste. Right now, 2 external hard drives with 8 TB cost around 400 euros.

The disk is aligned to sector 2048 (1024 K for logical sector 512 bytes) I understand that "pciide - bad" in red is because it is in IDE mode. Right now I have the system performing several operations and I cannot do tests, but the speed with the disk aligned usually ranges between 200 and 500 MB/s depending on whether TRIM is performed or not. In XP I have not noticed an increase in performance by doing TRIM with Solid State Doctor 3.0.3.2 (SSD Tools) but I have seen it by doing TRIM with SSD Tweaker Pro 4.0.1 .

These are the values for SDD Kingston A400 connected to SATA port, reported by various tools such as HDDscan & Eassos DiskGenius running on Windows 10 and the command "fsutil fsinfo sectorinfo": Sector Size: 512 Physical Sector Size: 512 However DiskAlignment Test says it is an AF disk and report: Logical block size: 512 bytes Physical block size: 4096 bytes I remember that when I first installed it a few years ago I had problems with partitions allocated to sector 63 that reduced its performance. It's curious the error rate of all the tools. So what I'm looking at is the AS SSD Benchmark Aliggment value in green or red ending in K, which corresponds to the size in KiB of the sectors prior to the indicated partition. That is, if it starts in sector 2048, it gives a value of 1024 K for disks with a logical sector of 512 bytes. That is, the value of the partition offset.