Need Windows XP users to test new eject utility (Update 2017-12-04)

Hope this is not too late. Followed your instructions to relace the eject.exe.

I don't usually use the eject on the platform so I don't know what the problem looked like previously

Tried the Platform's eject several times and worked.

Clicked eject and Platform closed but the drive did not eject.

Worked several times and then failed. Platform closed but drive did not eject.

Watching TaskManager and see eject start and then close and Platform close but drive did not eject.

Notice that an icon for USBDiskEjector remains in the TaskBar until try to hover over to see if it has a Tooltip. Eject.exe is not running at the time.

Then had a string where it failed to eject repeatedly.

Windows XP Home Edition SP3

Processors Information
-------------------------------------------------------------------------
Processor 1 ID = 0
Number of cores 1 (max 1)
Number of threads 1 (max 1)
Name Intel Core Solo
Codename Yonah
Specification Genuine Intel(R) CPU T1350 @ 1.86GHz
Package (platform ID) Socket 479 mPGA (0x5)
CPUID 6.E.8
Extended CPUID 6.E
Core Stepping C0
Technology 65 nm
Core Speed 1861.7 MHz
Multiplier x Bus Speed 14.0 x 133.0 MHz
Rated Bus speed 531.9 MHz
Stock frequency 1866 MHz
Instructions sets MMX, SSE, SSE2, SSE3
L1 Data cache 32 KBytes, 8-way set associative, 64-byte line size
L1 Instruction cache 32 KBytes, 8-way set associative, 64-byte line size
L2 cache 2048 KBytes, 8-way set associative, 64-byte line size
FID/VID Control yes
FID range 6.0x - 14.0x
Max VID 1.263 V

Chipset
-------------------------------------------------------------------------
Northbridge Intel i945GM rev. 03
Southbridge Intel 82801GHM (ICH7-M/U) rev. B0
Memory Type DDR2
Memory Size 512 MBytes
Channels Single
Memory Frequency 266.0 MHz (1:2)
CAS# latency (CL) 4.0
RAS# to CAS# delay (tRCD) 4
RAS# Precharge (tRP) 4
Cycle Time (tRAS) 12
Bank Cycle Time (tRC) 16
Host Bridge 0x27A0


but does not eject the drive. Wins XP sp3. I normally use the eject function of windows, but decided to try this to contribute some info.

Update: Renaming the new version to eject, not eject.exe seems to have fixed the problem initially, will keep trying it.

Also: the old one works for me too.