Jump to content

Recommended Posts

Posted

There are versions ported from Win8 (storahci.sys v6.2.9200.16384 and storahci.sys v6.2.9200.20652) but I actually don't remember testing them with the GPT Loader.

I will give them a try.


Posted
  On 4/16/2024 at 11:27 AM, Dave-H said:

Ah thanks. That's an older version of the Paragon driver than the one I have.
IIRC it was buggy, and the version 10 driver is much better.
:)

Expand  

This version is older than "Paragon HFS for Win v.10.5.0.95", the MAC system reader, also installs GPT on Windows XP with drivers updated to version 10.5.0.95 and seems to fix many issues from the previous version.

  On 4/16/2024 at 7:46 PM, Outbreaker said:
Expand  

I didn't know about this one, thanks.
What version is build based?
 

Posted

@roytam1

None of the storahci.sys drivers known to work in XP allow recognition of GPT disks.

Tried after installing the GPT_Loader with both storport.sys from Win7 (disk not even listed in Device Manager) and storport from Win8 (disk listed in Device Manager but no volume detected).

Same behavior even without installing the Paragon driver.

 

 

 

Posted
  On 4/17/2024 at 11:23 PM, Cixert said:

This version is older than "Paragon HFS for Win v.10.5.0.95", the MAC system reader, also installs GPT on Windows XP with drivers updated to version 10.5.0.95 and seems to fix many issues from the previous version.

I didn't know about this one, thanks.
What version is build based?
 

Expand  

Paragon HFS  v11.0.0.175 was still compatible with Windows XP only the installer wasn't. :lol:

Posted (edited)

I have done a test to check the behavior of the Paragon GPT Loader driver with the 2TB limit in an XP system configured in IDE mode.

After formatting my 4TB Seagate ST4000LM024 GPT disk in Win10, I started to fill it always in Win10 by copying in a progressive way the files numbered from 01 to 432 until to reach 2,194,897,825,792 bytes (at the end of the copy I made sure that all the files were uncorrupted):

4-TB-GPT-1-99-TB.png

 

After connecting the disk to the XP system with Paragon GPT Loader installed, I first verified again that all files were not corrupted and then copied a single file to the disk reaching a total of 2,199,889,600,512 bytes:

4-TB-GPT-over-2-TB.png

 

Checking once again the integrity of all files, I noticed that the first file copied a few days earlier (the one marked with the number 01) was now corrupt while all the others were intact. But on the next system reboot, here is what happened:

4-TB-GPT-Loader-fails.png

 

The problem encountered is almost the same as the one I detected using the asmedia asahci32.sys driver in a system configured in SATA/AHCI mode. The difference, which is no insignificant, is that at least with the asmedia driver, by following the identical procedure above, the drive was still accessible in XP and other files were still correctly available although the 2,199,023,255,552 bytes limit was exceeded.

 

At this point, I also have serious doubts whether the GPT Loader can effectively work on 3TB GPT disks. It certainly does not work on 4TB GPT disks.

 

Edited by Andalu
Posted (edited)
  On 4/22/2024 at 2:40 PM, Andalu said:

At this point, I also have serious doubts whether the GPT Loader can effectively work on 3TB GPT disks. It certainly does not work on 4TB GPT disks.

 

Expand  

If it is partitioned with a 2 TB limit, do you have problems?
For example, 4 TB hard drive divided into 2 partitions.

Edited by Cixert
Posted
  On 4/24/2024 at 2:06 AM, Cixert said:

If it is partitioned with a 2 TB limit, do you have problems?
For example, 4 TB hard drive divided into 2 partitions.

Expand  

Thanks for the suggestion, but splitting a disk into multiple partitions is not my goal. I would like to use a single partition. I really can't see my 16TB disk divided into 8 partitions.

Also, since the Paragon GPT Loader driver is supposed to work only by enabling IDE mode, which is no longer provided in modern systems, I don't think it's worth spending any more time on it.

 

  • 8 months later...
Posted (edited)

I'm back to testing with GPT.
Starting from the same point where I left off some time ago.
I think I partitioned the 6TB hard drive with Windows Seven and then unfragmented it.
https://msfn.org/board/topic/181911-read-gpt-hard-disk-on-windows-xp/page/5/#findComment-1251406

It's working fine on Windows XP (BIOS mode IDE-legacy) with a new installer I found for the Paragon 10.5.0.95 driver.

I installed it from Paragon Partition Manager 15 (aka 2015) Professional x86 v10.1.25.779 (2015-09-18)
This is the last version that contains Paragon GPT loader, in later versions it is not included.

Please suggest me what tests I can perform to verify that it works fine on Windows XP. The disk is divided into 6 partitions.
1-NTFS 1.42 TiB
2-exFAT 1.19 TiB
3-FAT32 107 GiB
4-FAT32 976 GiB
5-FAT32 488 GiB
6-FAT32 1.29 TiB

  On 4/16/2024 at 7:46 PM, Outbreaker said:
Expand  

With version 11.0.0.175 the GPT hard drive does not work well for me, Windows XP does not recognize FAT32 partitions.

Edited by Cixert
Posted

When I did my tests, I was using version 10.5.0.95 of the Paragon driver, which I still have installed on XP.

I can't comment on FAT32 partitions, as my 3TB disk was formatted with a single NTFS partition.

It appeared to work in XP, but the problem was that when I switched between XP and 10 on my multi-boot machine, the drive showed horrendous errors in chkdsk.

This might of course be OK in a single boot system, but for me, it was unusable.

A further complication for me was that the 3TB disk is in an enclosure connected via an add-in eSATA card, not connected directly to the motherboard.

However I never got it working correctly when I did try connecting it directly either.

:(

Posted (edited)
  On 12/30/2024 at 12:04 AM, Dave-H said:

When I did my tests, I was using version 10.5.0.95 of the Paragon driver, which I still have installed on XP.

I can't comment on FAT32 partitions, as my 3TB disk was formatted with a single NTFS partition.

It appeared to work in XP, but the problem was that when I switched between XP and 10 on my multi-boot machine, the drive showed horrendous errors in chkdsk.

This might of course be OK in a single boot system, but for me, it was unusable.

A further complication for me was that the 3TB disk is in an enclosure connected via an add-in eSATA card, not connected directly to the motherboard.

However I never got it working correctly when I did try connecting it directly either.

:(

Expand  

I currently have w2000-XP-Seven-10 multiboot
(Windows 10 is not so unmanageable if you install the Windows 2000 interface with Classic Shell and Retrobar)
GPT works perfectly on XP-Seven-10
ANY VERSION OF PARAGON DRIVER 10.5.0.95 DOES NOT WORK
GPT on XP only works with Paragon Partition Manager 15 Professional x86 v10.1.25.779!!!
I don't know what's changed but the errors don't occur like in the other versions, for example I have access to the FAT32 partitions and with Paragon HFS for Windows 10.5.0.95 the first thing I get at star is a blue screen that doesn't occur with Paragon Partition Manager 15 Professional x86 v10.1.25.779.

Edited by Cixert
Posted

Interesting.
I can't remember all the versions I tried in my tests, but from what you say, I should at least try to find a copy of v10.1.25.779.
I can't imagine that all the problems I had would go away with that version, but you never know!
:dubbio:

Posted
  On 12/30/2024 at 11:51 AM, Dave-H said:

Interesting.
I can't remember all the versions I tried in my tests, but from what you say, I should at least try to find a copy of v10.1.25.779.
I can't imagine that all the problems I had would go away with that version, but you never know!
:dubbio:

Expand  

The conclusion I've come to is that the other versions are limited to 2 TiB. That's why the other versions didn't read my FAT32 partitions, since they're just over 2 TiB.
Paragon Partition Manager 15 makes different changes to the registry.
I'm working without any problems at the moment.

Posted

OK.

I've found a copy of v10.1.25.779.

My next worry is, how do I replace the version I already have installed with the older one?
I suspect that the installer won't let me do it, and I'm very worried that if I uninstall the present version I then won't be able to boot, I'll just get an 'inaccessible boot device' BSOD.
How can I avoid that?
:dubbio:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...