Dave-H

OK, that has fixed it! The command window is closing again at the end though, instead of going back to the command prompt. One thing I have noticed is that Windows 8.1 seems to feel the need to scan drive I: quite often when it mounts. Why I'm not sure, as looking in the event log it never seems to actually find any problem! The scan is of course almost instantaneous anyway as it's such a small volume. The only other thing I must now try is to check that it all works OK on the other 4096 interface only machine, to make sure that there are still no complications caused by the network drive.

No, sadly your tool restores exactly the same garbled desktop. I'd certainly be using it if it didn't! I think once the "damage" has been done, the desktop cannot return to normal except by a reboot. When it's come back in the garbled state, whether it's restored by your tool, the ATI Control Panel, or by putting the machine to sleep and waking it again, it never looks right again, even though it is apparently back at its normal settings. The differences are the mouse cursor display (which may be a clue!) and the box of rubbish at the top left, which stays there, although proportionately larger, even if you go to DOS. Only a restart will clear it. That looks like some sort of corruption in the RAM of the graphics card.

Yes it does indeed, thanks Drugwash! Actually after I used it I realised that in fact the ATI Control Panel has a hot key function which will do exactly that same thing, so I'm actually now using that! Now when the display suddenly vanishes to I don't know what, I can just hit Ctrl+F12 and bring it back again, albeit with the square of digital rubbish in the top left hand corner, and a big blurry mouse cursor in a grey square box, as per my original screenshot! I've no found any way of returning it completely to normal apart from a reboot, but at least I can finish what I was doing easily now before rebooting. I'm still no nearer to finding out why it's doing what it's doing though. It would be a help to find exactly what triggers the problem! I have a program called Registry Workshop, which has a pop out menu that allows you to select favourite registry locations. Getting that to pop out and double clicking on any of the entries crashes the display pretty reliably! The other crashes seem to happen quite randomly after using Explorer for a while to move files around and that sort of thing. I've never managed to provoke a crash by using any other program (so far!)

OK, tried that, and what's happening with "run as an administrator" is this - Vista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sector* Volume 9 J RAW Partition 931 GB Healthy'dsfo' is not recognized as an internal or external command,operable program or batch file.'dsfo' is not recognized as an internal or external command,operable program or batch file. Checkpoint#1Press any key to continue . . .

Sorry for the long delay in replying again. I did manage to get the Asus ICM driver to work in Windows 98 after a bit of a struggle, but it didn't affect the problem I'm afraid. I've been experimenting with other earlier driver versions, but all the ones I've been able to find either have the same problem, or don't contain any hardware IDs for the card. I've tried manually adding the necessary information to the INF files, but without success. Catalyst 4.3, and possibly 4.4, are supposedly the last "proper" Windows 98 ATI drivers, but the card post-dates them. Catalyst 5.2 is a driver for ME which does support the card, but also crashes. I'm now working on the principle that it isn't actually a problem with the driver itself. It does install fine and works fine until you try something taxing, at which point it decides to switch spontaneously to some other output standard, which unfortunately my monitor can't display! It passes all the DirectX tests with flying colours, so it can't be that unstable.

Yes, changing the elevate.exe switch from -c to -k does exactly what I wanted! The window now stays open when the batch ends. I've tried just double clicking on the switcher file and that all works fine, which is good as it means it can be run from a shortcut, but there is a problem with right clicking and selecting "run as administrator". The command prompt window comes up OK after the UAC prompt is dismissed, it says what interface the disk is connected with, but then just outputs some lines that are too fast to read, and closes! Needless to say it hasn't done the switch.

That's all fine jaclaz, works a treat, both in elevated and non-elevated prompts! The only thing I would suggest is that when you are using a non-elevated prompt, a second command window opens when you dismiss the UAC prompt. That window closes itself when it's finished what it's doing and you "press any key to continue..." It might be nicer if it went back to the command prompt rather than just closing, so people could check its contents if they want to before closing it manually, especially considering that the first command window does stay open. I haven't tried just double clicking on the switcher file, or right clicking and running as an administrator. Would that now work? With regards to getting a bit of drive space back when using the 512 interface, I personally don't think that's important enough to complicate things over. I think we're only talking about a quarter of a gigabyte, and the disks being used nowadays are almost certainly going to be tens of gigabytes in size at least, so the extra would be a very small proportional increase in size. Especially as it will only work with one interface, I really wouldn't bother with it. As a matter of interest, if you did implement this, and the disk was being used on the 512 interface and data was written to the "extra" area, what would happen to that data when you switched to the 4096 interface? I assume it wouldn't be accessible, but would it be damaged? This has been a really fascinating exercise, and I've really enjoyed doing it!

Sorry for the delay, the site's been down again! I've tried the new version just in Windows 8.1 with elevated command prompts, and I'm delighted to say that it all seems to work perfectly, switching happily in either direction! This is the setup output - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>cd\mkprilogC:\mkprilog>mkprilogPlease input an approximated size in Megabytes for the FAT12 partition,minimum 1, maximum 32...The image will be created in the same folder as this batchand will be named PriLog.imgPlease consider how in the a size roughly 7 times the size of this partitionwill NOT be accessible/usable normally, in other words the PriLog.img oncedeployed will reduce disk capacity by 7 times the size you input, exampleIf you choose 1 Mbyte, you will lose roughly 7 Mbytes...If you choose 32 Mbyte, you will lose roughly 224 Mbytes32Writing MBR at offset 0 ...... done.Writing the 512 bytes/sector bootsector BPB at offset 32768 ...... done.Writing the 4096 bytes/sector bootsector BPB at offset 262144...... done.Writing FAT tables incipit ...... done.Press any key to continue . . ..The image should have been created as PriLog.img, now you need tomanually dd it to the destination disk, a suitable command would be:dsfi.exe \\.\PhysicalDrive[n] 0 0 PriLog.imgMake sure that you use the RIGHT Disk Number [n], do check in Disk Manager.The disk can be mounted indifferently through the 4kb or the 512 bytes/sectorinterface to deploy the image.Once the image has been deployed you may need to disconnect and reconnect thedisk to have the FAT12 volume be recognized and mounted to a drive letter.Then you can go to Disk Manager and create a Primary partition, NTFS formattedextending on all the available space on disk (or on just a portion of it).The size of the NTFS partition you create must be at least 7 times the size ofthe FAT12 one.It is "better" to use a Vista (or later) OS to create the NTFS partition asthe partition would be better if Megabyte aligned.(or do it manually or use a suitable third-party tool) as the XP will align iton head/cylinder boundaries, whilst a MB-aligned partition will be faster onslow buses such as USB 2.0The partition and the NTFS filesystem MUST be created when the disk is connectedas a 4kb sectored device, this is NOT negotiable.Once the second partition has been created, and I repeat, this MUST be donewith the device connected as 4kb sectored, you can run the mkdualdisk.cmdWhich will modify the disk and create the needed EPBR's.Press any key to continue . . .C:\mkprilog>dsfi \\.\PhysicalDrive5 0 0 PriLog.imgOK, written 33554432 bytes at offset 0C:\mkprilog>mkdualdisk"DUAL" disk found as \\.\PHYSICALDRIVE5Creating a temporary copy of the MBRdsfo \\.\PHYSICALDRIVE5 0 4096 temp.mbrOK, 4096 bytes, 0.016s, MD5 = c5e2a6e6a72dd713bde01cef7939e4ddNow the extent of the FAT12 partition is 65472000001B8h: 44 55 41 4C DUAL000001BEh: 00 00 00 00 0F 00 00 00 3F 00 00 00 01 00 00 00000001CEh: 00 00 00 00 01 00 00 00 40 00 00 00 C0 FF 00 00000001DEh: 00 14 11 04 07 FE FF FF 00 00 01 00 00 0B 8D 0E000001EEh: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00The disk was recognized as created with the Prilog schemeCreating a temporary copy of the NTFS partition bootsectordsfo \\.\PHYSICALDRIVE5 268435456 4096 tempNTFS.bssOK, 4096 bytes, 0.000s, MD5 = 13193b512259ee7256e9a592720f4821Press any key to continue . . .and copying it to the filedsfo tempNTFS.bss 0 0 as4kbNTFS.bssOK, 4096 bytes, 0.000s, MD5 = 13193b512259ee7256e9a592720f4821Creating a copy of the 4kb bytes/sector NTFS bootsectorAnd modifying it to become the 512 bytes/sector NTFS bootsectordsfo tempNTFS.bss 0 0 as512NTFS.bssOK, 4096 bytes, 0.000s, MD5 = 4476465c2498dd63a3c97e8a17cb6d21Press any key to continue . . .Creating a copy of the 4kb bytes/sector EPBRand writing to it the values for the NTFS volumeOK, 4096 bytes, 0.000s, MD5 = fc86b746e3b8c6f0108aaf1a1ac6271aCreating a copy of the 512 bytes/sector EPBRand writing to it the values for the NTFS volumeOK, 4096 bytes, 0.000s, MD5 = 620f0b67a91f7f74151bc5be745b7110Press any key to continue . . .Now we write the sectors to the diskdsfi \\.\PHYSICALDRIVE5 0 4096 Prilog.mbrOK, written 4096 bytes at offset 0dsfi \\.\PHYSICALDRIVE5 29672 4096 EPBR1_512.epbOK, written 4096 bytes at offset 29672dsfi \\.\PHYSICALDRIVE5 258048 4096 EPBR1_4Kb.epbOK, written 4096 bytes at offset 258048Deleting temporary files ...temp.mbr deletedtempNTFS.bss deletedPrilog.mbr deletedEPBR1_4kb.epb deletedEPBR1_512.epb deletedPress any key to continue . . .C:\mkprilog>This is switching from 4096 mode to 512 mode - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>I:I:\>switcherdaVista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 512 bytes/sectorNTFS volume found as \\.\Volume{e308684d-bc26-11e4-bfa7-00304879f908}, drive J:* Volume 9 J RAW Partition 931 GB HealthyRemoving drive letter J: ...The current NTFS bootsector is NOT the 512 bytes oneswitching it ...dsfi \\.\Volume{e308684d-bc26-11e4-bfa7-00304879f908} 0 4096 as512NTFS.bssOK, written 4096 bytes at offset 0Please wait while DiskPart scans your configuration...Leaving DiskPart...* Volume 9 New Volume NTFS Partition 931 GB HealthyMounting the volume to a drive letter...Checking drive letters ...In use: C: D: E: F: G: H: I: S: W:Free : J: K: L: M: N: O: P: Q: R: T: U: V: X: Y: Z:Mounting volume to first free drive letter J: ...OK, done:* Volume 9 J New Volume NTFS Partition 931 GB HealthyPress any key to continue . . .I:\>This is switching back to 4096 mode, with is what failed before - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>I:I:\>switcherdaVista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sectorNTFS volume found as \\.\Volume{e308684d-bc26-11e4-bfa7-00304879f908}, drive J:* Volume 9 J RAW Partition 931 GB HealthyRemoving drive letter J: ...The current NTFS bootsector is NOT the 4kb bytes oneswitching it ...dsfi \\.\Volume{e308684d-bc26-11e4-bfa7-00304879f908} 0 4096 as4kbNTFS.bssOK, written 4096 bytes at offset 0Please wait while DiskPart scans your configuration...Leaving DiskPart...* Volume 9 New Volume NTFS Partition 931 GB HealthyMounting the volume to a drive letter...Checking drive letters ...In use: C: D: E: F: G: H: I: S: W:Free : J: K: L: M: N: O: P: Q: R: T: U: V: X: Y: Z:Mounting volume to first free drive letter J: ...OK, done:* Volume 9 J New Volume NTFS Partition 931 GB HealthyPress any key to continue . . .I:\>Unfortunately we're not quite there yet as I then tried with a non-elevated command prompt and got this in the second window - Vista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 512 bytes/sectorNTFS volume found as \\.\Volume{e308684d-bc26-11e4-bfa7-00304879f908}, drive J:File not found - I:\ELEVATEDCannot access file I:\+ECHO is off.Houston, we've had a problem.The current NTFS bootsector is already the 512 bytes oneCannot access file I:\elevatedECHO is off.Mounting the volume to a drive letter...Checking drive letters ...In use: C: D: E: F: G: H: I: J: S: W:Free : K: L: M: N: O: P: Q: R: T: U: V: X: Y: Z:The parameter is incorrect.Oh, oh, something prevented the correct mounting to K: ...Cannot access file I:\elevatedECHO is off.Press any key to continue . . .Looking at it, I immediately thought that there must be a typo somewhere in the switcher file resulting in an invalid path, but I can't see any obvious one.

Well I don't understand what's changed. All I did was change the ":do_switchDA" section in the switcherda file to your new version, and add the lockdismount file to drive I:. I ran the commands you stated, and got this - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>diskpartMicrosoft DiskPart version 6.3.9600Copyright (C) 1999-2013 Microsoft Corporation.On computer: ASHFIELDCOURTDISKPART> select disk 5Disk 5 is now the selected disk.DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 0 Extended 4096 B 252 KB Partition 1 Primary 254 MB 256 KB Partition 2 Primary 931 GB 32 MBDISKPART> exitLeaving DiskPart...C:\WINDOWS\system32>I:I:\>lockdismount -lock 5 dsfi \\.\PhysicalDrive5 33554432 4096 as4kbNTFS.bssLocking volume I: ...FAILED (Access is denied.)Operation failed!Please close all files/applications accessing the affected volumes and try again.I:\>diskpartMicrosoft DiskPart version 6.3.9600Copyright (C) 1999-2013 Microsoft Corporation.On computer: ASHFIELDCOURTDISKPART> rescanPlease wait while DiskPart scans your configuration...DiskPart has finished scanning your configuration.DISKPART> select disk 5Disk 5 is now the selected disk.DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 0 Extended 4096 B 252 KB Partition 1 Primary 254 MB 256 KB Partition 2 Primary 931 GB 32 MBDISKPART> exitLeaving DiskPart...I:\>

I had rolled back the "official" KB3013455, but I reinstalled it before applying the new version. All fine and the fonts all look great again, although I did have to re-do the ClearType tuning. Thanks so much from me too harkaz!

Yes, I wondered about that too. Wouldn't it have been better to keep the same version number as the faulty version of the file on the "fixed" version? Then Windows Update will just think you've got the "official" faulty version installed.

Sorry for the delay again, tried the last option with lockdismount and the modified script, but no joy I'm afraid. Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>I:I:\>switcherdaVista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sectorThe NTFS volume has not been found.This may seemingly happen on 8.x, and we can then try with direct access.No dice, something is really wrong.Press any key to continue . . .I:\>

Sorry, I didn't mean that they were exactly the same file, just different versions of the same file, which is what I should have said of course! I'm sure you're right about why they're offering both. If you do the later version first, the earlier one presumably won't do anything, and if you do the earlier version first the other version will update it of course.

Strange that the KB article offers two files for download, KB3013455 and KB3037639, and it says to install both of them, and that it doesn't matter what order you install them in. "There is no installation order requirement for the two updates that are discussed in this article (KB3013455 and KB3037639)." As they both replace the same single system file, I find that rather odd!

I tried substituting the win32k.sys file from KB3037639 (5.2.3790.5534) onto my system into the System32 and DLLCache folders, and was rewarded with a BSOD when the desktop was due to load. Stop 21A (Fatal System Error). "The session manager initialisation system process terminated unexpectedly with a status of 0xc0000263." It looks like a no go sadly, but I wasn't really expecting to be able to just replace a 5.1 file with a 5.2 file. I hope MS do roll out a fix for 5.1 systems, as surely the font corruption must be a serious issue even on POS systems.

Actually it's showing up in Device Manager as ASUS VE278! Where Windows is getting this from I don't know, as there are no INF files with that string in them anywhere. I guess it must be getting it directly from the monitor's embedded hardware information. In Windows XP it just appears as a generic Plug and Play monitor! Yes, using the VGA connector.

OK, this is what I get switching from 4096-512 on PC181512 - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>I:I:\>switcherdaVista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 512 bytes/sectorNTFS volume found as \\.\Volume{c8aa1940-b5e8-11e4-bf9c-00304879f908}, drive J:* Volume 9 J RAW Partition 931 GB HealthyRemoving drive letter J: ...The current NTFS bootsector is NOT the 512 bytes oneswitching it ...dsfi \\.\Volume{c8aa1940-b5e8-11e4-bf9c-00304879f908} 0 4096 as512NTFS.bssOK, written 4096 bytes at offset 0Please wait while DiskPart scans your configuration...Leaving DiskPart...* Volume 9 New Volume NTFS Partition 931 GB HealthyMounting the volume to a drive letter...Checking drive letters ...In use: C: D: E: F: G: H: I: S: W:Free : J: K: L: M: N: O: P: Q: R: T: U: V: X: Y: Z:Mounting volume to first free drive letter J: ...OK, done:* Volume 9 J New Volume NTFS Partition 931 GB HealthyPress any key to continue . . .I:\>And this is what I get trying to go the other way from 512-4096 on PC1814096 - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>I:I:\>switcherdaVista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sectorThe NTFS volume has not been found.This may seemingly happen on 8.x, and we can then try with direct access.The current NTFS bootsector is NOT the 4kb bytes oneswitching it ...dsfi \\.\PHYSICALDRIVE5 33554432 4096 as4kbNTFS.bss\\.\PHYSICALDRIVE5 - Access is denied.attempting to run a rescanOn computer: ASHFIELDCOURTPlease wait while DiskPart scans your configuration...DiskPart has finished scanning your configuration.This is the most we can do, if after next iterationthe NTFS volume is still not found but the bootsectoris detected as the "right" one, you will need todisconnect the disk through "Safely Remove Hardware" andreconnect it ...Press any key to continue . . ."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sectorThe NTFS volume has not been found.This may seemingly happen on 8.x, and we can then try with direct access.The current NTFS bootsector is NOT the 4kb bytes oneswitching it ...dsfi \\.\PHYSICALDRIVE5 33554432 4096 as4kbNTFS.bss\\.\PHYSICALDRIVE5 - Access is denied.attempting to run a rescanOn computer: ASHFIELDCOURTPlease wait while DiskPart scans your configuration...DiskPart has finished scanning your configuration.This is the most we can do, if after next iterationthe NTFS volume is still not found but the bootsectoris detected as the "right" one, you will need todisconnect the disk through "Safely Remove Hardware" andreconnect it ...Press any key to continue . . ."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sectorThe NTFS volume has not been found.This may seemingly happen on 8.x, and we can then try with direct access.The current NTFS bootsector is NOT the 4kb bytes oneswitching it ...dsfi \\.\PHYSICALDRIVE5 33554432 4096 as4kbNTFS.bss\\.\PHYSICALDRIVE5 - Access is denied.attempting to run a rescanOn computer: ASHFIELDCOURTPlease wait while DiskPart scans your configuration...DiskPart has finished scanning your configuration.This is the most we can do, if after next iterationthe NTFS volume is still not found but the bootsectoris detected as the "right" one, you will need todisconnect the disk through "Safely Remove Hardware" andreconnect it ...Press any key to continue . . ."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sectorThe NTFS volume has not been found.This may seemingly happen on 8.x, and we can then try with direct access.The current NTFS bootsector is NOT the 4kb bytes oneswitching it ...dsfi \\.\PHYSICALDRIVE5 33554432 4096 as4kbNTFS.bss\\.\PHYSICALDRIVE5 - Access is denied.attempting to run a rescanOn computer: ASHFIELDCOURTPlease wait while DiskPart scans your configuration...DiskPart has finished scanning your configuration.This is the most we can do, if after next iterationthe NTFS volume is still not found but the bootsectoris detected as the "right" one, you will need todisconnect the disk through "Safely Remove Hardware" andreconnect it ...Press any key to continue . . .Endlessly repeated of course........ Ejecting the disk's USB connection and re-connecting makes no difference, again the large partition doesn't appear, with the same result from the switcher output. It's still being shown in Disk Management as a primary partition with no file system.

Actually no monitor INF was ever supplied with my monitor, which is an ASUS VE278Q. It's never used one before so I'd be surprised if it's the cause of the problem now, and it is the same one I was using before I changed the motherboard. I had been thinking it was maybe some sort of memory issue, although it's only a 256 MB card, and I thought that it was only 512 MB and higher cards that Windows 98 really struggled with. I did get a 512 MB AGP nVidia card working very happily with Windows 98 with my old motherboard.

OK, here's the DISKPART test run with PC181512bs4096 - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>diskpartMicrosoft DiskPart version 6.3.9600Copyright (C) 1999-2013 Microsoft Corporation.On computer: ASHFIELDCOURTDISKPART> select disk 5Disk 5 is now the selected disk.DISKPART> detail diskWDC WD10 EZEX-00BN5A0 SCSI Disk DeviceDisk ID: 4C415544Type : SATAStatus : OnlinePath : 0Target : 0LUN ID : 0Location Path : PCIROOT(0)#PCI(1E00)#PCI(0300)#ATA(C00T00L00)Current Read-only State : NoRead-only : NoBoot Disk : NoPagefile Disk : NoHibernation File Disk : NoCrashdump Disk : NoClustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 8 I FAT Partition 31 MB Healthy Volume 9 J RAW Partition 931 GB HealthyDISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 0 Extended 512 B 31 KB Partition 1 Primary 31 MB 32 KB Partition 2 Primary 931 GB 32 MBDISKPART> select partition 2Partition 2 is now the selected partition.DISKPART> detail partitionPartition 2Type : 07Hidden: NoActive: NoOffset in Bytes: 33554432 Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- --------* Volume 9 J RAW Partition 931 GB HealthyDISKPART> list volume Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 G DVD-ROM 0 B No Media Volume 1 H DVD-ROM 0 B No Media Volume 2 F CAPTURE FAT32 Partition 55 GB Healthy Volume 3 C Windows 8.1 NTFS Partition 119 GB Healthy System Volume 4 S NTFS Dump NTFS Partition 59 GB Healthy Pagefile Volume 5 W WIN98 WINXP FAT32 Partition 102 GB Healthy Volume 6 D WINXP BOOT FAT32 Partition 34 GB Healthy Volume 7 E ARCHIVE FAT32 Partition 279 GB Healthy Volume 8 I FAT Partition 31 MB Healthy* Volume 9 J RAW Partition 931 GB HealthyDISKPART> exitLeaving DiskPart...C:\WINDOWS\system32>This time after I switched the disk to bs4096 in XP and then went to the 512 connection and rebooted into 8.1 there were no anomalies, the large partition was shown as unformatted as expected.

This is really strange! I went back to PC1XP4096 so I could switch the drive back to bs4096, which I can't do on 8.1. That worked fine, and I then checked the big partition showed as unformatted when switched to PC1XP512, left it connected like that, and rebooted into 8.1. To my great surprise the two drives appeared correctly in PC181512, even though the large partition should have been shown as unformatted as it was left set as bs4096! Disk Manager said it's a primary partition as before, but this time formatted and assigned letter J:. The only oddity was that the large J: drive now had a file added to it "bootsqm.dat" which looks like something from CHKDSK. I switched to PC1814096, and both the drives were still apparently OK using the other interface! Disk Manager however was now showing a blank entry for the drive, with no partitions shown, and the size displayed on the left under the disk number was a ridiculous negative figure! I could still apparently access the drives in Explorer quite happily though. I then switched back to PC181512, and the system immediately threw a BSOD "NMI_HARDWARE_FAILURE". I rebooted and it was OK, thank goodness. Running the DISKPART test (still connected PC181512bs4096) then gave - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>diskpartMicrosoft DiskPart version 6.3.9600Copyright (C) 1999-2013 Microsoft Corporation.On computer: ASHFIELDCOURTDISKPART> select disk 5Disk 5 is now the selected disk.DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 0 Extended 512 B 31 KB Partition 1 Primary 31 MB 32 KB Partition 2 Primary 931 GB 32 MBDISKPART>So, I don't know what's going on here at all now, I hope this gives you some clue!

Yes on PC1XP4096 I'm getting this - Microsoft Windows XP [Version 5.1.2600](C) Copyright 1985-2001 Microsoft Corp.C:\XP User Files\Dave>diskpartMicrosoft DiskPart version 5.1.3565Copyright (C) 1999-2003 Microsoft Corporation.On computer: AshfieldCourtDISKPART> select disk 5Disk 5 is now the selected disk.DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 Extended 4096 B 252 KB Partition 2 Logical 931 GB 32 MB Partition 3 Primary 254 MB 256 KBDISKPART> exitLeaving DiskPart...C:\XP User Files\Dave>And on PC1814096, just rebooting into a different OS without changing anything else, I'm getting this - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>diskpartMicrosoft DiskPart version 6.3.9600Copyright (C) 1999-2013 Microsoft Corporation.On computer: ASHFIELDCOURTDISKPART> select disk 5Disk 5 is now the selected disk.DISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 0 Extended 4096 B 252 KB Partition 1 Primary 254 MB 256 KB Partition 2 Primary 931 GB 32 MBDISKPART>BTW I think what we're doing now, just using the one machine (PC1) with both interfaces is much better than swapping between machines, as it has removed any possible confusion caused by the network drive on the other machine, and the different drive letters being assigned on the two machines.

OK, here's what I got (PC1814096) - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>diskpartMicrosoft DiskPart version 6.3.9600Copyright (C) 1999-2013 Microsoft Corporation.On computer: ASHFIELDCOURTDISKPART> select disk 5Disk 5 is now the selected disk.DISKPART> detail diskWDC WD10 EZEX-00BN5A0 USB DeviceDisk ID: 4C415544Type : USBStatus : OnlinePath : 0Target : 0LUN ID : 0Location Path : UNAVAILABLECurrent Read-only State : NoRead-only : NoBoot Disk : NoPagefile Disk : NoHibernation File Disk : NoCrashdump Disk : NoClustered Disk : No Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 8 I FAT Partition 254 MB HealthyDISKPART> list partition Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 0 Extended 4096 B 252 KB Partition 1 Primary 254 MB 256 KB Partition 2 Primary 931 GB 32 MBDISKPART> select partition 2Partition 2 is now the selected partition.DISKPART> detail partitionPartition 2Type : 07Hidden: NoActive: NoOffset in Bytes: 33554432There is no volume associated with this partition.DISKPART> list volume Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 G DVD-ROM 0 B No Media Volume 1 H DVD-ROM 0 B No Media Volume 2 F CAPTURE FAT32 Partition 55 GB Healthy Volume 3 C Windows 8.1 NTFS Partition 119 GB Healthy System Volume 4 S NTFS Dump NTFS Partition 59 GB Healthy Pagefile Volume 5 W WIN98 WINXP FAT32 Partition 102 GB Healthy Volume 6 D WINXP BOOT FAT32 Partition 34 GB Healthy Volume 7 E ARCHIVE FAT32 Partition 279 GB Healthy Volume 8 I FAT Partition 254 MB HealthyDISKPART> exitLeaving DiskPart...C:\WINDOWS\system32>mountvol>mountvol.logC:\WINDOWS\system32>reg query hklm\system\mounteddevices>regexe.logC:\WINDOWS\system32>And here's the two logs. Logs.zip

All still OK on XP, although there is a long pause at one point in the batch where a "please wait" might be good. Same problem on 8.1 though, although now when I try to switch from 512 to 4096 I just get - Microsoft Windows [Version 6.3.9600](c) 2013 Microsoft Corporation. All rights reserved.C:\WINDOWS\system32>I:I:\>switcherngVista , or later, ...OK, I am a local admin ..."DUAL" disk found as \\.\PHYSICALDRIVE5Disk is connected as 4096 bytes/sectorTHe NTFS volume has not been found.Press any key to continue . . .I:\>The drive is still not showing up correctly in Disk Management of course, so can't be seen as it apparently has no file system or drive letter.

OK, I've now done some more tests with Windows 8.1. This time I concentrated just on the primary machine, on which I can use both interfaces. On the USB (4096) interface it behaves exactly the same as the secondary machine. It seems that everything is fine in Windows XP, but in Windows 8.1 it is possible to switch from 4096 to 512, but not the other way. I left it switched to 4096 using XP, then went to 8.1, and the smaller drive was recognised OK (although it said it had errors and needed to be scanned as the secondary machine had done) but the larger partition didn't appear, and again appears in Disk Management as an unformatted primary partition. I can switch it to 512 OK and it then works, but trying to switch back just produces "the parameter is incorrect" again, so I can only switch back using XP. In XP the large partition appears as a logical drive in an extended partition, as it should. Could this be anything to do with poor (or lack of) support for this on Windows 8.1? I noticed very early on when I started working with 8.1 that it doesn't seem to be possible to create extended partitions and logical drives using Disk Management as you can in XP. It only seems to create primary partitions, at least on simple volumes.

Thanks Oldbie! Sorry, I should have mentioned of course, but forgot, that I use the same card (but with a later driver) on Windows XP, and it always works perfectly. I can use it on Windows 8.1 as well, although I don't normally, and it's no problem there either (different (64 bit) driver again of course!) I've therefore no reason to think that there's anything physically wrong with the card. The monitor resolution (1920x1080 60Hz) is the same now as it was with the old motherboard, so that hasn't changed either.