I have my Pegasus 3 R8 hooked up to my mac Mini, but my new windows machine has thunderbolt ports also. Am I able to move the Pegasus 3 to my windows machine? I suspect I need something that allows windows to read HFS also.
Can I hook up my Pegasus 3 to my Windows machine?
- 392 Views
- Last Post 17 May 2023
- Topic Is Solved
It is recommended to take a backup of your data, reformat and use the Pegasus on your window machine.You will need to install the driver and reformat the unit with the pegasus promise utility to NTFS . Refer to the product manual for more information
Product Manual
https://www.promise.com/DownloadFile.aspx?DownloadFileUID=4547
Pegasus3 series driver for Windows (Windows 10 & 11)
https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6873
Pegasus Promise Utility
https://www.promise.com/DownloadFile.aspx?DownloadFileUID=6919
Thank you.
So basically
1. Take a backup from the mac mini
2. Move the enclosure to the windows machine with the driver and utility installed
3, Reformat to NTFS
4, Restore the data
5. Live happily ever after
yes?
Basically ,take a backup of your data from the Pegasus R8 before you move it to your windows machine, reformat and restore the data back into the Pegasus.
Hi Eric,
One additional note, if you want to use the volume on both MAC and Windows, you might want to consider using the exFAT filesystem. It's supported by both Windows and macOS.
macOS does support NTFS, but the NTFS volume will mount read-only. An exFAT volume will mount read-write.
Hi again, I have now finally purchased a Intel NUC (Intel NUC 13 Pro Kit NUC13ANKi7) it is a 13th gen i7 with Thunderbolt. I installed Windows 11 Pro.
I downloaded what I think are the latest drivers and utility:
- R_WinDrv_Installer_V6.2.0.18_WHQL
- PROMISE_Utility_Pro_23.4.1
The enclosure connects to the NUC and I get a blue light and the lightning symbol is lit.
I cannot connect to it using the utility however and when I look at the device manager the driver has the yellow triangle with an error code of 55:
This device is blocked from starting while the user is not logged in. (Code 55)
The almighty Google reports that this may happen if you run BitLocker and The Kernel DMA Protection at the same time. I have disabled both, but the driver still fails to load.
I find 2 events in the event viewer:
Info:
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9c205a39-1250-487d-abd7-e831c6290539}" />
<EventID>400</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2023-05-16T13:51:37.5504981Z" />
<EventRecordID>495</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="236" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>Media-NUC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="DeviceInstanceId">PCI\VEN105A&DEV8870&SUBSYS4300105A&REV01\6&4ecd7d2&0&00080038</Data>
<Data Name="DriverName">oem36.inf</Data>
<Data Name="ClassGuid">{4d36e97b-e325-11ce-bfc1-08002be10318}</Data>
<Data Name="DriverDate">10/26/2022</Data>
<Data Name="DriverVersion">6.2.0.18</Data>
<Data Name="DriverProvider">Promise Technology, Inc.</Data>
<Data Name="DriverInbox">false</Data>
<Data Name="DriverSection">stex_Instmsi.NTamd64</Data>
<Data Name="DriverRank">0xff0001</Data>
<Data Name="MatchingDeviceId">PCI\VEN105A&DEV8870&SUBSYS_4300105A</Data>
<Data Name="OutrankedDrivers" />
<Data Name="DeviceUpdated">false</Data>
<Data Name="Status">0x0</Data>
<Data Name="ParentDeviceInstanceId">PCI\VEN8086&DEV1578&SUBSYS8870105A&REV00\0F7B812045E9070008</Data>
</EventData>
</Event>
Error:
Device PCI\VEN_105A&DEV_8870&SUBSYS_4300105A&REV_01\6&4ecd7d2&0&00080038 had a problem starting.
Driver Name: oem36.inf
Class Guid: {4d36e97b-e325-11ce-bfc1-08002be10318}
Service: stexstpt
Lower Filters:
Upper Filters:
Problem: 0x0
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9c205a39-1250-487d-abd7-e831c6290539}" />
<EventID>411</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2023-05-16T13:51:37.5613491Z" />
<EventRecordID>496</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="236" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>Media-NUC</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="DeviceInstanceId">PCI\VEN105A&DEV8870&SUBSYS4300105A&REV01\6&4ecd7d2&0&00080038</Data>
<Data Name="DriverName">oem36.inf</Data>
<Data Name="ClassGuid">{4d36e97b-e325-11ce-bfc1-08002be10318}</Data>
<Data Name="ServiceName">stexstpt</Data>
<Data Name="LowerFilters" />
<Data Name="UpperFilters" />
<Data Name="Problem">0x0</Data>
<Data Name="Status">0xc00000e5</Data>
</EventData>
</Event>
I had to enter BIOS and turn off VT-d, then the driver loaded and the array was available to Windows.