Real HD detection issue (3.6.1)

[bladecgn]

Hi! Tried the 4.0.x branch.

My 32 GF CF (RDB) is not detected / selctable any more.

Of course as always started WinUAE in admin mode. Does anyone have the same issue?

[bladecgn]

Originally Posted by AC/DC HACKER!

I'm now using http://www.winuae.net/files/b/winuae_4010b1.7z and my 32GB CF is noticed fine. I have 2 for my A4000 CSPPC, and both are read.. Also used HDToolBox to make changes and so far, is doing as it should.

I haven't used Admin with Windows 7 x64 in a long time. But that also does fine so far.

Hmmh... The device that used to show up before with the RDB CF-Card does not show up any more (in the add harddisks panel). Here are Logs of the Config that works with Winuae 3.x but not 4.x.

[Toni Wilen]

Originally Posted by bladecgn

Hmmh... The device that used to show up before with the RDB CF-Card does not show up any more (in the add harddisks panel). Here are Logs of the Config that works with Winuae 3.x but not 4.x.

Attach also logs from last working version.

[bladecgn]

Originally Posted by Toni Wilen

Attach also logs from last working version.

Thanks for looking into this. Here are the requested logs from the working version.

[bladecgn]

Here you are


Interestingly without default.cfg the CF is selectable in 4.0.1 now but does not boot.

[Toni Wilen]

Do you mean 3.6.1 and 4.0.0 also do not work? (working is from 3.6.0)

[bladecgn]

Originally Posted by Toni Wilen

Do you mean 3.6.1 and 4.0.0 also do not work? (working is from 3.6.0)

Didn't try 3.6.1... shall I?

[Toni Wilen]

Originally Posted by bladecgn

Didn't try 3.6.1... shall I?

Yes! Both 3.6.1 and 4.0.0.

[bladecgn]

Originally Posted by Toni Wilen

Yes! Both 3.6.1 and 4.0.0.

3.6.1 also NOT working. Didn't give 4.0.0 a try because of that.

[Toni Wilen]

Moved. Obviously was in wrong thread originally

[Toni Wilen]

Could you test which 3.6.1 beta introduced the problem? I can't see anything obvious in logs or changes..

EDIT: after some more log checking..

hd ignored, read error 1110!

1110 = ERROR_MEDIA_CHANGED.

Do you have any other CF adapter? Above error seems like adapter got very confused, perhaps it does not properly fail unsupported commands like ATA passthrough commands that WinUAE tries. It also returned 121 = ERROR_SEM_TIMEOUT which does not sound too good.

If you insert FAT formatted CF (that Windows detects and can be used to read-write), does the card also disappear in Windows if you attempt to mount it in WinUAE?

[bladecgn]

Already beta 3.6.1 is not working.

Different CF Reader works. But I want to use the before working adapter in the future if possible.

[bladecgn]

Originally Posted by bladecgn

Already beta 3.6.1 is not working.

Different CF Reader works. But I want to use the before working adapter in the future if possible.

CF Fat formatted does not disappear.

[Toni Wilen]

I need to know its id values (VID and PID) so I can black list it. I don't do any other workarounds for bad hardware. (Should be available somewhere deep in Windows device manager. Yes, not very helpful but I don't remember..)

(FAT probably works because it is already mounted in Windows, preventing WinUAE to get exclusive lock so "Lock" option is needed)

[bladecgn]

"usb\vid_0aec&pid_3260\200510050841571ld"



vid: 0aec
pid: 3260

[bladecgn]

With latest beta all is working again!!

Thanks so much for your continuous effort, Toni.
I really appreciate your great work!

[AC/DC HACKER!]

Originally Posted by bladecgn

Already beta 3.6.1 is not working.

Different CF Reader works. But I want to use the before working adapter in the future if possible.

I also had a dysfunctional reader a long time ago. Don't buy CHEAP! HA!