Dave-H Posted February 20, 2024 Posted February 20, 2024 18 hours ago, Andalu said: If I didn't look wrong, I read in your motherboard user manual that there are two options in the bios: "Option ROM Scan" and "ROM Scan Ordering". In order to get the Blu-ray player connected to the asmedia card as a boot device, do you have already set the first option on "Enabled" and/or the second on "Add-On first"?I'm asking just to make sure we've tried every possibility for your motherboard. This is what I have in my BIOS. The ROM Scan Ordering is set to 'Onboard First' as you can see. The other option is 'Addon First'. There doesn't seem to be an 'Option ROM Scan' option in my BIOS, but the BIOS options can change of course depending on the configuration of the machine, type of processor etc. I haven't tried changing the option. I did try as an experiment connecting the Blu-ray drive to the eSATA port on the other Silicon Image card in the machine, the one I used to connect the external disk enclosure to. To my surprise, it wasn't recognised at all, it was like it didn't exist! No sign of it in the BIOS still, and not in the XP Explorer or Disk Management. I didn't try in Windows 10, but I guess the result would have been the same. I tried updating the driver in XP using the one on the disk which came with the card. It went through the motions and then said 'Windows cannot open this program because it has been prevented by a software restriction policy.' I don't know what to do about that. 2
Dave-H Posted February 20, 2024 Posted February 20, 2024 7 hours ago, Andalu said: All asahci32.sys driver versions should work with the asmedia ASM1061 card in XP, from the first v1.1.7.110 to the last v3.2.0. I would try installing v1.1.7.110 also in Win98 if only to leave no stone unturned. Please consider that each driver should give a good result for the GPT disk recognition but with differences for the safely remove feature. For example, it is not available in the v3.2.0 on the asus Z790 (I have to use the HotSwap! utility) while the dvd-rom drive is still recognized as removable drive. I've been trying other drivers on XP, with no success I'm afraid. The version 1.1.7.110 driver wouldn't install at all. If I run the setup, it runs briefly and then just closes, with no messages on screen. This might have been because there was already a later version of the driver installed. Version 3.2.0 was even worse, it apparently installed, but then there was a BSOD, MACHINE_CHECK_EXCEPTION. On reboot, the machine started OK, but nothing seemed to have changed. In Device Manager, the Asmedia card now showed driver version 3.2.0.0, but on inspecting the driver files it was still using asahci32.sys version 2.0.3.0001 as it was before. Trying another update from the INF file just produced a system freeze. I then tried reinstalling the original 2.0.4 driver. That said another stalled installation needed to be rolled back, which it did and the system froze again! It rebooted OK, and I then manually cleaned the registry of the previous driver installations and started from scratch again with the 2.0.4 driver, which then installed fine. I don't think I'll be trying that again! There was no evidence at all that version 1.1.7.110 was 98 compatible, in fact the INF file specifically says that it isn't, so I'm not even going to try! 2
Dave-H Posted February 20, 2024 Posted February 20, 2024 @jaclaz Do we now think that this file system corruption when going between operating systems is an intrinsic problem? What I could do is to try temporarily connecting the disk in the enclosure directly to the motherboard, and make sue it's powered all the time that the system is on, so it will be just like it was a fixed internal drive. If I use it like that and see if the corruption still occurs, that should at least prove whether the problem is being caused by the connection via the card or not. 2
Andalu Posted February 21, 2024 Posted February 21, 2024 @Dave-H I am sorry that you had problems with the installation of the different versions of the asmedia drivers and had to waste time to remove them. I will try not to suggest that you try other drivers.... is a promise
jaclaz Posted February 21, 2024 Posted February 21, 2024 @Dave-H I don't know, the errors your CHKDSK reported are too "narrow" to be (IMHO) attributed to "generic" connection/transmission issues, they are all about cross-linked files, they sound more like some issues at filesystem level, if it was a cable (let's say the riser) picking up some interferences you would probably have had "different" errors, a cross-linked file, a wrong entry in $MFT, an actually corrupted file, a truncated file, etc. jaclaz
Dave-H Posted February 21, 2024 Posted February 21, 2024 11 hours ago, Andalu said: @Dave-H I am sorry that you had problems with the installation of the different versions of the asmedia drivers and had to waste time to remove them. I will try not to suggest that you try other drivers.... is a promise Please don't blame yourself! It was a perfectly reasonable thing to do, to try other drivers to see if they made any difference to the issues. I'm really not at all sure why trying to install the 3.2.0 driver caused so much problem, it says quite specifically that it's XP compatible, and the installer certainly didn't say otherwise. What I should have probably done is completely uninstall the existing driver and clean the system of it before installing 3.2.0, rather than trying to install 3.2.0 over the top of it. I still don't understand why the driver on the disk that came with the card won't install because of a 'software restriction policy'. That is very puzzling. I did try changing that BIOS option BTW, but it seemed to make no difference to anything. I do think that the important thing now is to track down the cause of this file system corruption that I'm seeing when going between XP and 10. If that can't be explained, the whole thing is useless anyway, so there's no point in playing with different drivers and cards. 1
Dave-H Posted February 21, 2024 Posted February 21, 2024 4 hours ago, jaclaz said: @Dave-H I don't know, the errors your CHKDSK reported are too "narrow" to be (IMHO) attributed to "generic" connection/transmission issues, they are all about cross-linked files, they sound more like some issues at filesystem level, if it was a cable (let's say the riser) picking up some interferences you would probably have had "different" errors, a cross-linked file, a wrong entry in $MFT, an actually corrupted file, a truncated file, etc. jaclaz Thanks. What I will do I think is put the 3TB disk into one of the internal caddies that I use for one of the other drives on the system. That is connected directly to the motherboard and is permanently powered, so it will just appear as a normal internal directly SATA connected disk. If that continues to have the corruption problem, I would have thought that the number one suspect has to be the Paragon GPT driver, as surely it should work fine natively in Windows 10.
mina7601 Posted February 21, 2024 Posted February 21, 2024 2 hours ago, Dave-H said: I still don't understand why the driver on the disk that came with the card won't install because of a 'software restriction policy'. 18 hours ago, Dave-H said: It went through the motions and then said 'Windows cannot open this program because it has been prevented by a software restriction policy.' I don't know what to do about that. Check if you actually have set up software restrictions in Group Policy before attempting the methods below. https://www.instructables.com/Getting-past-Software-Restriction-Policies/
Dave-H Posted February 21, 2024 Posted February 21, 2024 Thanks, but there are no restrictions set up in Group Policy. I've done many other installs which have had no problem, so why that particular one has an issue I have no idea. I did copy the files from the CD to the hard drive and run it from there as well as running from the CD directly, and the result was the same. IIRC there was some mention in the installer log that something wasn't signed, but usually if that's the case you get an option dialogue box to ignore that. Not in this case. 2
Dave-H Posted February 21, 2024 Posted February 21, 2024 (edited) @jaclaz @Andalu OK, I've now connected the 3TB drive directly to my motherboard. All seemed well in XP, the drive was there in Explorer, with the correct drive letter.. I did a backup to it, which apparently went fine. I then ran chkdsk on it, and all was fine. No sign of the drive being in use when I ran chkdsk this time BTW. I then booted into Windows 10, the drive was there, fine. Without doing anything, I ran chkdsk on the drive, and to my horror got this! CHKDSK.txt So I think that proves that the problem is nothing to do with the connection method! It appears that Window XP, with the Paragon GPT driver, is writing to the drive in such a way that it appears badly corrupted to Windows 10. Once again, chkdsk did not run automatically when I booted into Windows 10, which is in itself very strange as one of the fixed drives was obviously badly corrupted! The only reason I can think of to explain that is that the corruption only occurred after the system had finished booting, which surely isn't likely to be the case. If this can't be resolved, it's useless. I will now try the same thing the other way around! Edited January 29 by Dave-H Excessively large code box replaced with text file! 1
jaclaz Posted February 21, 2024 Posted February 21, 2024 Well, the idea was to run CHKDSK without parameters (it doesn't mean "with the /f parameter"). Even without the /F parameter the CHKDSK (which in theory, without parameters is running in "read only" mode) does make some corrections BUT (mostly) only lists the issues and asks to be re-run with the /F parameter. Running it without parameters on one OS, then re-rerunning it without parameters on the other should give an idea about these issues being "real" or "artifacts" of the one (or the other) CHKDSK/NTFS version. If you run with the /F parameter and it fixes the issue, the issue is not there anymore, the other OS should not detect it, and when you go back to the first it should not be able to find it (the same one) anymore (as it was fixed). If each OS fixes the issues (differently) you risk to enter an endless flip-flop. I would expect that the SAME issue (uncorrected) would be detected on both OS. jaclaz 1
Andalu Posted February 21, 2024 Posted February 21, 2024 @Dave-H I thought you had already uninstalled the Paragon driver. I had reported in one of my posts: "The Paragon GPT driver is no longer needed." The drivers needed for GPT disks recognition are disk.sys v5.2.3790.4006 (mandatory) from Win2003, partmgr.sys v5.2.3790.4171 from Win2003, scsiport.sys v5.1.2600.6073 and the asmedia driver. On my systems the Paragon driver has never allowed recognition of GPT disks.
Dixel Posted February 21, 2024 Posted February 21, 2024 I should advise against unnecessary manipulations with that 3TB Seagate DeathStar 2.0 @D.Draker already warned about. This could be fatal for that potentially weak HDD. 4
Dave-H Posted February 21, 2024 Posted February 21, 2024 36 minutes ago, jaclaz said: Well, the idea was to run CHKDSK without parameters (it doesn't mean "with the /f parameter"). Even without the /F parameter the CHKDSK (which in theory, without parameters is running in "read only" mode) does make some corrections BUT (mostly) only lists the issues and asks to be re-run with the /F parameter. Running it without parameters on one OS, then re-rerunning it without parameters on the other should give an idea about these issues being "real" or "artifacts" of the one (or the other) CHKDSK/NTFS version. If you run with the /F parameter and it fixes the issue, the issue is not there anymore, the other OS should not detect it, and when you go back to the first it should not be able to find it (the same one) anymore (as it was fixed). If each OS fixes the issues (differently) you risk to enter an endless flip-flop. I would expect that the SAME issue (uncorrected) would be detected on both OS. jaclaz OK, this is the result with chkdsk in read-only mode. Microsoft Windows [Version 10.0.19045.4046] (c) Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>chkdsk t: The type of the file system is NTFS. Volume label is BACKUP. WARNING! /F parameter not specified. Running CHKDSK in read-only mode. Stage 1: Examining basic file system structure ... Attribute record (80, "") from file record segment 14E0C is corrupt. Attribute record (80, "") from file record segment 14E11 is corrupt. Attribute record (80, "") from file record segment 14E13 is corrupt. Attribute record (80, "") from file record segment 14E18 is corrupt. Attribute record (80, "") from file record segment 14E19 is corrupt. Attribute record (80, "") from file record segment 14E1A is corrupt. Attribute record (80, "") from file record segment 14E1B is corrupt. Attribute record (80, "") from file record segment 14E6C is corrupt. Attribute record (80, "") from file record segment 14E70 is corrupt. Attribute record (80, "") from file record segment 14E76 is corrupt. Attribute record (80, "") from file record segment 14E78 is corrupt. Attribute record (80, "") from file record segment 14E7D is corrupt. Attribute record (A0, $I30) from file record segment 14E9E is corrupt. Attribute record (A0, $I30) from file record segment 14EFD is corrupt. Attribute record (A0, $I30) from file record segment 14EFE is corrupt. Attribute record (A0, $I30) from file record segment 14F05 is corrupt. Attribute record (A0, $I30) from file record segment 14F12 is corrupt. Attribute record (A0, $I30) from file record segment 14F21 is corrupt. Attribute record (A0, $I30) from file record segment 14F2E is corrupt. Attribute record (A0, $I30) from file record segment 14F48 is corrupt. Attribute record (A0, $I30) from file record segment 14F4B is corrupt. Attribute record (A0, $I30) from file record segment 15037 is corrupt. Attribute record (A0, $I30) from file record segment 15042 is corrupt. Attribute record (A0, $I30) from file record segment 15048 is corrupt. Attribute record (A0, $I30) from file record segment 1504F is corrupt. Attribute record (A0, $I30) from file record segment 15073 is corrupt. Attribute record (A0, $I30) from file record segment 15074 is corrupt. Attribute record (A0, $I30) from file record segment 15091 is corrupt. Attribute record (A0, $I30) from file record segment 150A8 is corrupt. Attribute record (A0, $I30) from file record segment 150C5 is corrupt. Attribute record (A0, $I30) from file record segment 150CF is corrupt. Attribute record (A0, $I30) from file record segment 150ED is corrupt. Attribute record (A0, $I30) from file record segment 150F5 is corrupt. Attribute record (A0, $I30) from file record segment 15107 is corrupt. Attribute record (A0, $I30) from file record segment 15108 is corrupt. Attribute record (A0, $I30) from file record segment 15134 is corrupt. Attribute record (A0, $I30) from file record segment 15142 is corrupt. Attribute record (A0, $I30) from file record segment 15168 is corrupt. Attribute record (A0, $I30) from file record segment 15199 is corrupt. Attribute record (A0, $I30) from file record segment 151D2 is corrupt. Attribute record (A0, $I30) from file record segment 151D3 is corrupt. Attribute record (A0, $I30) from file record segment 151EC is corrupt. Attribute record (A0, $I30) from file record segment 1521D is corrupt. Attribute record (A0, $I30) from file record segment 15272 is corrupt. Attribute record (A0, $I30) from file record segment 1A3BB is corrupt. Attribute record (A0, $I30) from file record segment 1A407 is corrupt. Attribute record (A0, $I30) from file record segment 1A429 is corrupt. Attribute record (A0, $I30) from file record segment 1A434 is corrupt. Attribute record (A0, $I30) from file record segment 1A435 is corrupt. Attribute record (80, "") from file record segment 1A781 is corrupt. Attribute record (80, "") from file record segment 1A791 is corrupt. Attribute record (80, "") from file record segment 1A7DD is corrupt. Attribute record (80, "") from file record segment 1A844 is corrupt. Attribute record (80, "") from file record segment 1A855 is corrupt. Attribute record (80, "") from file record segment 1A85F is corrupt. Attribute record (80, "") from file record segment 1A863 is corrupt. Attribute record (80, "") from file record segment 1A864 is corrupt. Attribute record (80, "") from file record segment 1A867 is corrupt. Attribute record (80, "") from file record segment 1A869 is corrupt. Attribute record (80, "") from file record segment 1A870 is corrupt. Attribute record (80, "") from file record segment 1A877 is corrupt. Attribute record (80, "") from file record segment 1A879 is corrupt. Attribute record (80, "") from file record segment 1A87B is corrupt. Attribute record (80, "") from file record segment 1A87E is corrupt. Attribute record (80, "") from file record segment 1A882 is corrupt. Attribute record (80, "") from file record segment 1A889 is corrupt. Attribute record (80, "") from file record segment 1A88A is corrupt. Attribute record (80, "") from file record segment 1A88B is corrupt. Attribute record (80, "") from file record segment 1A88D is corrupt. Attribute record (80, "") from file record segment 1A896 is corrupt. Attribute record (80, "") from file record segment 1A8A4 is corrupt. Attribute record (80, "") from file record segment 1A8A6 is corrupt. Attribute record (80, "") from file record segment 1A8B0 is corrupt. Attribute record (A0, $I30) from file record segment 1AA4D is corrupt. Attribute record (80, "") from file record segment 1AA5E is corrupt. Attribute record (80, "") from file record segment 1AA63 is corrupt. Attribute record (80, "") from file record segment 1AA81 is corrupt. Attribute record (80, "") from file record segment 1AA82 is corrupt. Attribute record (80, "") from file record segment 1AA83 is corrupt. Attribute record (80, "") from file record segment 1AA85 is corrupt. Attribute record (80, "") from file record segment 1AA86 is corrupt. Attribute record (80, "") from file record segment 1AA87 is corrupt. Attribute record (80, "") from file record segment 1AA88 is corrupt. Attribute record (80, "") from file record segment 1AA8A is corrupt. Attribute record (80, "") from file record segment 1AA8B is corrupt. Attribute record (80, "") from file record segment 1AA8C is corrupt. Attribute record (80, "") from file record segment 1AA8D is corrupt. Attribute record (80, "") from file record segment 1AA8E is corrupt. Attribute record (80, "") from file record segment 1AA8F is corrupt. Attribute record (80, "") from file record segment 1AA90 is corrupt. Attribute record (80, "") from file record segment 1AA91 is corrupt. Attribute record (80, "") from file record segment 1AA92 is corrupt. Attribute record (80, "") from file record segment 1AA93 is corrupt. Attribute record (80, "") from file record segment 1AA95 is corrupt. Attribute record (80, "") from file record segment 1AABA is corrupt. Attribute record (80, "") from file record segment 1AABC is corrupt. Attribute record (80, "") from file record segment 1AABE is corrupt. Attribute record (80, "") from file record segment 1AABF is corrupt. Attribute record (80, "") from file record segment 1AAC0 is corrupt. Attribute record (80, "") from file record segment 1AAC1 is corrupt. Attribute record (80, "") from file record segment 1AAC3 is corrupt. Attribute record (80, "") from file record segment 1AAC4 is corrupt. Attribute record (80, "") from file record segment 1AAC5 is corrupt. Attribute record (80, "") from file record segment 1AAC6 is corrupt. Attribute record (80, "") from file record segment 1AAC7 is corrupt. Attribute record (80, "") from file record segment 1AAC8 is corrupt. Attribute record (80, "") from file record segment 1AAC9 is corrupt. Attribute record (80, "") from file record segment 1AACA is corrupt. Attribute record (80, "") from file record segment 1AACB is corrupt. Attribute record (80, "") from file record segment 1AACC is corrupt. Attribute record (80, "") from file record segment 1AACD is corrupt. Attribute record (80, "") from file record segment 1AAD0 is corrupt. Attribute record (80, "") from file record segment 1AAD1 is corrupt. Attribute record (80, "") from file record segment 1AAD2 is corrupt. Attribute record (80, "") from file record segment 1AAD3 is corrupt. Attribute record (80, "") from file record segment 1AAD4 is corrupt. Attribute record (80, "") from file record segment 1AAD5 is corrupt. Attribute record (80, "") from file record segment 1AAD7 is corrupt. Attribute record (80, "") from file record segment 1AAD8 is corrupt. Attribute record (80, "") from file record segment 1AAD9 is corrupt. Attribute record (80, "") from file record segment 1AADA is corrupt. Attribute record (80, "") from file record segment 1AADB is corrupt. Attribute record (80, "") from file record segment 1AADC is corrupt. Attribute record (80, "") from file record segment 1AADD is corrupt. Attribute record (80, "") from file record segment 1AADE is corrupt. Attribute record (80, "") from file record segment 1AAE0 is corrupt. Attribute record (80, "") from file record segment 1AAE1 is corrupt. Attribute record (80, "") from file record segment 1AAE2 is corrupt. Attribute record (80, "") from file record segment 1AAE3 is corrupt. Attribute record (80, "") from file record segment 1AAE4 is corrupt. Attribute record (80, "") from file record segment 1AAE5 is corrupt. Attribute record (80, "") from file record segment 1AAE6 is corrupt. Attribute record (80, "") from file record segment 1AAE7 is corrupt. Attribute record (80, "") from file record segment 1AAE8 is corrupt. Attribute record (80, "") from file record segment 1AAE9 is corrupt. Attribute record (80, "") from file record segment 1AAEA is corrupt. Attribute record (80, "") from file record segment 1AAEB is corrupt. Attribute record (80, "") from file record segment 1AAEC is corrupt. Attribute record (80, "") from file record segment 1AAED is corrupt. Attribute record (80, "") from file record segment 1AAEE is corrupt. Attribute record (80, "") from file record segment 1AAEF is corrupt. Attribute record (80, "") from file record segment 1AAF0 is corrupt. Attribute record (80, "") from file record segment 1AAF1 is corrupt. Attribute record (80, "") from file record segment 1AAF2 is corrupt. Attribute record (80, "") from file record segment 1AAF3 is corrupt. Attribute record (80, "") from file record segment 1AAF4 is corrupt. Attribute record (80, "") from file record segment 1AAF5 is corrupt. Attribute record (80, "") from file record segment 1AAF6 is corrupt. Attribute record (80, "") from file record segment 1AAF7 is corrupt. Attribute record (80, "") from file record segment 1AAF8 is corrupt. Attribute record (80, "") from file record segment 1AAF9 is corrupt. Attribute record (80, "") from file record segment 1AAFA is corrupt. Attribute record (80, "") from file record segment 1AAFB is corrupt. Attribute record (80, "") from file record segment 1AAFC is corrupt. Attribute record (80, "") from file record segment 1AAFD is corrupt. Attribute record (80, "") from file record segment 1AAFE is corrupt. Attribute record (80, "") from file record segment 1AAFF is corrupt. Attribute record (80, "") from file record segment 1AB00 is corrupt. Attribute record (80, "") from file record segment 1AB01 is corrupt. Attribute record (80, "") from file record segment 1AB02 is corrupt. Attribute record (80, "") from file record segment 1AB03 is corrupt. Attribute record (80, "") from file record segment 1AB04 is corrupt. Attribute record (80, "") from file record segment 1AB05 is corrupt. Attribute record (80, "") from file record segment 1AB06 is corrupt. Attribute record (80, "") from file record segment 1AB07 is corrupt. Attribute record (80, "") from file record segment 1AB08 is corrupt. Attribute record (80, "") from file record segment 1AB09 is corrupt. Attribute record (80, "") from file record segment 1AB0A is corrupt. Attribute record (80, "") from file record segment 1AB0B is corrupt. Attribute record (80, "") from file record segment 1AB0C is corrupt. Attribute record (80, "") from file record segment 1AB0D is corrupt. Attribute record (80, "") from file record segment 1AB0E is corrupt. Attribute record (80, "") from file record segment 1AB0F is corrupt. Attribute record (80, "") from file record segment 1AB10 is corrupt. Attribute record (80, "") from file record segment 1AB11 is corrupt. Attribute record (80, "") from file record segment 1AB12 is corrupt. Attribute record (80, "") from file record segment 1AB13 is corrupt. Attribute record (80, "") from file record segment 1AB14 is corrupt. Attribute record (80, "") from file record segment 1AB15 is corrupt. Attribute record (80, "") from file record segment 1AB16 is corrupt. Attribute record (80, "") from file record segment 1AB17 is corrupt. Attribute record (80, "") from file record segment 1AB18 is corrupt. Attribute record (80, "") from file record segment 1AB19 is corrupt. Attribute record (80, "") from file record segment 1AB1A is corrupt. Attribute record (80, "") from file record segment 1AB1B is corrupt. Attribute record (80, "") from file record segment 1AB1C is corrupt. Attribute record (80, "") from file record segment 1AB1D is corrupt. Attribute record (80, "") from file record segment 1AB1E is corrupt. Attribute record (80, "") from file record segment 1AB1F is corrupt. Attribute record (80, "") from file record segment 1AB20 is corrupt. Attribute record (80, "") from file record segment 1AB21 is corrupt. Attribute record (80, "") from file record segment 1AB22 is corrupt. Attribute record (80, "") from file record segment 1AB23 is corrupt. Attribute record (80, "") from file record segment 1AB24 is corrupt. Attribute record (80, "") from file record segment 1AB25 is corrupt. Attribute record (80, "") from file record segment 1AB26 is corrupt. Attribute record (80, "") from file record segment 1AB40 is corrupt. Attribute record (80, "") from file record segment 1AB41 is corrupt. Attribute record (80, "") from file record segment 1AB42 is corrupt. Attribute record (80, "") from file record segment 1AB49 is corrupt. Attribute record (80, "") from file record segment 1AB64 is corrupt. Attribute record (80, "") from file record segment 1AB90 is corrupt. Attribute record (80, "") from file record segment 1AB9D is corrupt. Attribute record (80, "") from file record segment 1ABCB is corrupt. Attribute record (80, "") from file record segment 1ABCD is corrupt. Attribute record (80, "") from file record segment 1ABD2 is corrupt. Attribute record (80, "") from file record segment 1AC15 is corrupt. Attribute record (80, "") from file record segment 1ACAD is corrupt. 109824 file records processed. File verification completed. Phase duration (File record verification): 6.55 seconds. 2 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. Errors found. CHKDSK cannot continue in read-only mode. C:\WINDOWS\system32> 1
Dave-H Posted February 21, 2024 Posted February 21, 2024 26 minutes ago, Andalu said: @Dave-H I thought you had already uninstalled the Paragon driver. I had reported in one of my posts: "The Paragon GPT driver is no longer needed." The drivers needed for GPT disks recognition are disk.sys v5.2.3790.4006 (mandatory) from Win2003, partmgr.sys v5.2.3790.4171 from Win2003, scsiport.sys v5.1.2600.6073 and the asmedia driver. On my systems the Paragon driver has never allowed recognition of GPT disks. So sorry, I hadn't picked up that, or if I did, I had forgotten about it! If it's likely to be the cause of the issue, I will certainly uninstall the Paragon driver. Where can I get the Win2003 files from? 26 minutes ago, Dixel said: I should advise against unnecessary manipulations with that 3TB Seagate DeathStar 2.0 @D.Draker already warned about. This could be fatal for that potentially weak HDD. He may have been right, but I'm not quite ready to condemn the disk itself yet! Of course if this proves to be unresolvable, the disk would certainly be a prime suspect as the culprit. 1
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now