Cixert Posted January 16 Author Posted January 16 3 hours ago, Multibooter said: Paragon Partition Manager 15 Professional x86 v10.1.25.779 is the most recent build of v15 I have come across. Paragon Hard Disk Manager 15 also has a "GPT Loader" selection in its installation menu. I have various builds of Paragon Hard Disk Manager 15 in my archive, among them: v10.1.25.779 (Suite, 32bit, 9Sep2015) v10.1.25.813 (Professional, 299-PRE, 19Nov2015) and v10.1.25.813 (Premium, 299-PME, 11Nov2015) v10.1.25.1125 (Professional, 799-PRE, 12Apr2017) v10.1.25.1137 (Professional, 799-PRE, 24Apr2017) Maybe the more recent build 813 contains an improved GPT Loader? A new release 813, only 2 months after build 779, indicates serious issues with build 779. Build 813 is the last build for SSE-only. I had installed build 813 on my SSE-only Pentium 3 laptop, but removed it again because the Linux ext3 partitions created by Paragon Partition Manager 15 were displayed as BAD by Symantec PartitionMagic 8.05, i.e. the ext3 partitions created by Paragon HDM 15 are not compatible with PartitionMagic, i.e. not backward-compatible with Win98 software. Once installed you can check the contents of the "gpt_loader" folder to see if it is different. I have downloaded the demo versions but these do not come with the driver.
Andalu Posted January 16 Posted January 16 7 hours ago, Cixert said: Oops, sorry. I don't know what could be wrong. My disk.sys version is different, it's 5.1.2600.5512. Although this seems unlikely to be the reason. I currently have a Toshiba HDWD260 "6Tb hard disk" with 6 exFAT partitions. The physical sector size is 512 bytes, most likely on that Seagate it is 4096 bytes. I initialized the drive quite a while ago, I think from Windows Seven and then defragmented the partitions. The first partition is 1.42 TiB and the rest are smaller. I also have the hard disk connected directly to the motherboard with IDE mode. In some kind of initial test I also had the BSOD occurred for gpt_lo~1.sys but then it has not happened again. All my disks have 4096 bytes per physical sector so I have no possibility to make tests with a disk that has 512 bytes per physical sector. My drive is also connected directly to the motherboard via sata port and the bios is configured in IDE Mode. 2 hours ago, Cixert said: @Andalu tell me what method you used to copy and verify files. I will try to replicate it to check what happens. In my current test and the previous one with gpt_loader v11.0.0.175 I simply copied the large part of the files in Win10 and the next one in XP. In both cases I used explorer.exe via classic copy and paste. These are many video files contained in various folders. To verify that the copied files are uncorrupted, I use the MediaInfo utility. If any files have problems, it shows a window without the video data. Really simple and quick. That is why I use video files. Once I have identified the corrupt ones, I do a comparison between the two SHA-1 codes, the one from the original file and the one that became corrupted. In no case did MediaInfo show incorrect results.
Andalu Posted January 16 Posted January 16 3 hours ago, Multibooter said: Paragon Partition Manager 15 Professional x86 v10.1.25.779 is the most recent build of v15 I have come across. Paragon Hard Disk Manager 15 also has a "GPT Loader" selection in its installation menu. I have various builds of Paragon Hard Disk Manager 15 in my archive, among them: v10.1.25.779 (Suite, 32bit, 9Sep2015) v10.1.25.813 (Professional, 299-PRE, 19Nov2015) and v10.1.25.813 (Premium, 299-PME, 11Nov2015) v10.1.25.1125 (Professional, 799-PRE, 12Apr2017) v10.1.25.1137 (Professional, 799-PRE, 24Apr2017) Maybe the more recent build 813 contains an improved GPT Loader? A new release 813, only 2 months after build 779, indicates serious issues with build 779. Build 813 is the last build for SSE-only. I had installed build 813 on my SSE-only Pentium 3 laptop, but removed it again because the Linux ext3 partitions created by Paragon Partition Manager 15 were displayed as BAD by Symantec PartitionMagic 8.05, i.e. the ext3 partitions created by Paragon HDM 15 are not compatible with PartitionMagic, i.e. not backward-compatible with Win98 software. Some time ago I did the test with the Paragon driver v11.0.0.175 without success: https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/23/#findComment-1263977 so I wanted to try version 10.1.25.779 which @Cixert found to work properly even when exceeding the limit of 2TB of data copied to the disk.
Multibooter Posted January 16 Posted January 16 (edited) 1 hour ago, Cixert said: Once installed you can check the contents of the "gpt_loader" folder to see if it is different. I have downloaded the demo versions but these do not come with the driver. I have restored the original WinXP SP3 disk.sys, partmgr.sys and sp3.cab on my SSE-only Pentium 3. I installed .NET Framework 4 because this is required by Paragon Hard Disk Manager 15. I don't like software requiring .NET Framework. I then installed Paragon Hard Disk Manager 15 v10.1.25.813 (Premium, 299-PME, 11Nov2015), entered the registration details, and selected only GPT Loader in the installation menu (I did not select Paragon Hard Disk Manager and did not select HotCore Driver). The installation was under Total Uninstall, for identifying the registry entries etc made during the installation, and for a clean uninstall. I do not have any HDD >2TB. The GPT Loader seems to read and write OK with a 1TB GPT HDD in a docking station connected via eSATA to an eSATA PC Card. I don't have \gpt_loader\ from other builds of Paragon Hard Disk Manager. Here is the MD5 of the 3 files in the folder of build 813: MD5 checksums of Paragon Hard Disk Manager 15 build 813: gpt_loader.sys: B0AFB269EBA85F9EC264035640319138 gpt_loader.inf: B04C4E8E712B6CB283C4AB1C53F06226 gpt_loader.cat: 9FC7222187B2A809C21E543E928686BE BTW, Total Uninstall lists 150.30MB space used by the installation when only the GPT Loader is selected. The main culprit is a 143MB .msi in \Documents and Settings\ Edited January 17 by Multibooter
Multibooter Posted January 16 Posted January 16 (edited) 1 hour ago, Andalu said: Some time ago I did the test with the Paragon driver v11.0.0.175 without success: https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/23/#findComment-1263977 so I wanted to try version 10.1.25.779 which @Cixert found to work properly even when exceeding the limit of 2TB of data copied to the disk. Paragon 16 v11 does not install/work under WinXP, requires a more recent opsys, if I remember right. No idea about the GPT loader v11 from MediaFire, it is digitally signed OK. Maybe v11.0.0.175 is for Toshiba HDDs? Toshiba is mentioned in "Installer v1.0.2.cmd" Edited January 17 by Multibooter
Cixert Posted January 17 Author Posted January 17 (edited) 47 minutes ago, Multibooter said: I installed .NET Framework 4 because this is required by Paragon Hard Disk Manager 15. I don't like software requiring .NET Framework. I don't have \gpt_loader\ from other builds of Paragon Hard Disk Manager. Here is the MD5 of the 3 files in the folder of build 813: MD5 checksums of Paragon Hard Disk Manager 15 build 813: gpt_loader.sys: B0AFB269EBA85F9EC264035640319138 gpt_loader.inf: B04C4E8E712B6CB283C4AB1C53F06226 gpt_loader.cat: 9FC7222187B2A809C21E543E928686BE BTW, Total Uninstall lists 150.30MB space used by the installation when only the GPT Loader is selected. The main culprit is a 143MB .msi in \Documents and Settings\ No paragon version has asked me .Net Framework 4.0 These require C++. MD5 checksums of Paragon Hard Disk Manager 15 build 779: gpt_loader.sys > MD5: B0AFB269EBA85F9EC264035640319138 gpt_loader.inf > MD5: B04C4E8E712B6CB283C4AB1C53F06226 gpt_loader.cat > MD5: 9FC7222187B2A809C21E543E928686BE The values are the same, can you also upload the MD5 value of... install_xp.reg > MD5: ED75D2BD6084EAD84A9ADABD4BD241DD install.reg > MD5: 22AA73696C1D1E4FFF650FC606A2192F install_xp.reg Make changes in the registry to avoid BSOD on Fat32 Boot, maybe some more change. 41 minutes ago, Multibooter said: Paragon 16 v11 does not install/work under WinXP, requires a more recent opsys, if I remember right. Maybe something got corrupted? This is a fork version, it was commented here. https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/22/#findComment-1263483 @Andalu I am reading other forum publications that report a 2TIB Limit for NTFS. I will verify that. What cluster size are you using to format, 4 KiB? Edited January 17 by Cixert
Andalu Posted January 17 Posted January 17 1 hour ago, Multibooter said: Paragon 16 v11 does not install/work under WinXP, requires a more recent opsys, if I remember right. No idea about the GPT loader v11 from MediaFire, it is digitally signed OK. Maybe v11.0.0.175 is for Toshiba HDDs? Toshiba is mentioned in "Installer v1.0.2.cmd" I do not know the version uploaded on Mediafire. I got that version of the Paragon driver from an earlier XP release from Ramsey. The .sys file has MD5: 75238FAEB1B5B13E6EB577B79DAAD3D9. As reported, even with that version, the data still gets corrupted.
Andalu Posted January 17 Posted January 17 (edited) 58 minutes ago, Cixert said: @Andalu I am reading other forum publications that report a 2TIB Limit for NTFS. I will verify that. What cluster size are you using to format, 4 KiB? Yes, the cluster size of the test disk is 4KB. Edited January 17 by Andalu
Cixert Posted January 17 Author Posted January 17 (edited) 17 hours ago, Andalu said: As a final note, during the first stage of copying files in XP, the bsod 0x00000024 occurred for gpt_lo~1.sys This BSOD is described here, it seems that the 2 patches would have to be applied to improve the system http://hardwarefetish.com/524-paragon-gpt_loadersys-bsod-analysis-and-fix I am not very clear on how the patches are applied. It says that a bak file of gpt_loader.sys is created, but I don't know if the bak is the good one, the bad one, or if it needs to be renamed. It is necessary to apply the 2 patches and with each patch a bak file is created. http://hardwarefetish.com/777-paragon-gpt-loader-3 Edited January 17 by Cixert
Dave-H Posted January 17 Posted January 17 Finally a report from me! I connected my caddy/enclosure directly to the motherboard instead of via the eSATA card. I've tested with the 3TB disk, and it works fine. I've written to it using Windows Explorer both using Windows XP and Windows 10, and have gone over 2TB on the drive, and I can't fault it. It passes chkdsk on XP and 10, no sign of the horrendous errors that I was getting before. So, it looks as if using the earlier version of the Paragon GPT driver was indeed the fix for that, thank you so much @Cixert! Now all I've got to do is find out why XP cannot see the disk correctly when it's connected via the card, when Windows 10 can! It can't be the hardware, so it must be the Silicon Image 32 bit XP driver. My search continues to resolve that, but at least I now know that the disk will work with XP once I get that sorted out. 1
Multibooter Posted January 17 Posted January 17 13 hours ago, Cixert said: No paragon version has asked me .Net Framework 4.0 These require C++. MD5 checksums of Paragon Hard Disk Manager 15 build 779: gpt_loader.sys > MD5: B0AFB269EBA85F9EC264035640319138 gpt_loader.inf > MD5: B04C4E8E712B6CB283C4AB1C53F06226 gpt_loader.cat > MD5: 9FC7222187B2A809C21E543E928686BE The values are the same, can you also upload the MD5 value of... install_xp.reg > MD5: ED75D2BD6084EAD84A9ADABD4BD241DD install.reg > MD5: 22AA73696C1D1E4FFF650FC606A2192F I had first attempted to install Paragon Hard Disk Manager 15 build 813 without having installed .NET FrameWork 4, but the installation stopped with the msg: ".NET 4.0 not found. Please install .NET 4.0 for further installation of the product" After having installed .NET Framework 4 the installation completed OK. The installer also modified I:\WINXPSP2\Microsoft.NET\Framework\v4.0.30319\ngen_service.log I can also confirm that build 813 requires MS Visual C ++ 2010 x86 Redistributable v10.0.40219, which was already installed on my SSE-only Pentium 3 laptop. (this specific build of C++ Redist is required). install_xp.reg and install.reg of Hard Disk Manager 15 build 813 have the same MD5 values as those of your build 779. The MD5 checksum of vid_custom.dll, also in the install-to, is CFC582BB605FFF80C2BACD5D43C0E485 Total Uninstall indicates a quite sophisticated installation, when just the GPT Loader is selected for installation with build 813. For example, 7 .exe files are added to \Windows\Installer\{619A89DE-5F01-11E2-85E8-000C2982512D}\ and a lot of registry entries. \Windows\Installer\d80b3.msi was also added by the installer and is digitally signed by Paragon 11Nov2015 but the signature is not valid. d80b3.msi is 6,334,976 bytes and has the MD5 B253CAE901F0D54D962DEF76E219135E and contains, among others, the 7 .exe files. 1
Multibooter Posted January 17 Posted January 17 On 1/10/2024 at 12:02 PM, Dave-H said: The eSATA interface card is a Silicon Image 3512 SATALink controller. As far as I can see it is using the latest driver 1.3.71.1, from 2008. I will keep looking to see if there's a later one. I am using driver 1.3.68.2 of 13Apr2007 under WinXP for the Vantec eSATA PC Card (has a Silicon Image Sil 3512 SATALink Controller) in my SSE-only Pentium 3 laptop, has worked great with HDDs <2TB. It came on the original driver CD of the eSATA PC Card. Under Win98 I use v1.3.65.2. Where did you find v1.3.71.1?
Cixert Posted January 17 Author Posted January 17 (edited) @Andalu In NTFS one partition formated with cluster 4KiB I have tested up to 2.2 TiB with "H2testw" and the result is perfect. No problems, no data corruption, no BSOD. Afterwards I added 0.5 TiB with videos and tested Mediainfo, the information given by Mediainfo is correct. If your data is secure you should do a test with H2testw to clear up any doubts. Make sure in the Device Manager that the hard disk is working with the driver version 8.0.1.0. @Multibooter It's not unusual for you to be asked for .Net 4 and not for me. It's possible that I have some residual files from my previous installation of .NET Framework, I don't know. Other programs that require .NET 4 ask me to install it. I think the last version compatible with Windows XP is 813 for Hard Disk Manager, I haven't found an installer for Partition Manager (last 779). Only in WinPE version. @Dave-H Finally, I'm glad it works. Please keep us posted if you manage to get the eSATA adapter working as well. What physical sector size does your hard disk have? Model? Edited January 17 by Cixert
Dave-H Posted January 17 Posted January 17 3 hours ago, Multibooter said: I am using driver 1.3.68.2 of 13Apr2007 under WinXP for the Vantec eSATA PC Card (has a Silicon Image Sil 3512 SATALink Controller) in my SSE-only Pentium 3 laptop, has worked great with HDDs <2TB. It came on the original driver CD of the eSATA PC Card. Under Win98 I use v1.3.65.2. Where did you find v1.3.71.1? The card that my external enclosure is connected to is a SiI 3132 card. I do also have a 3512 card in the system, but that's being used for two other disks. Sorry for the confusion, I was trying a lot of different hardware configurations at the time of the post you quoted! On XP, the 3132 card is using driver version 1.0.22.3 from 2008. Both of my SiI cards are Vantec.
Dave-H Posted January 17 Posted January 17 28 minutes ago, Cixert said: @Dave-H Finally, I'm glad it works. Please keep us posted if you manage to get the eSATA adapter working as well. What physical sector size does your hard disk have? Model? I will check on the 3TB drive and let you know.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now