Generated ghost drives problem
Generated ghost drives problem
Hi,
I am using HxC SD Emulator rev F with EPSON PC-586RV.
PC-586 is PC-9801 compatible computer, internal FDD is 2 drives (drive 0, 1) and external FDD is 2 drives(drive 2, 3).
PC-586's original internal FDD is EPSON SMD-340 or MITSUMI D353T3.
External FDD is PC-9801 compatible interface, available to PC-9801 general external FDD.
I connected HxC to the drives 0 and 1, and nothing connected drives 2 and 3.(see attached connecting diagram)
The ghost drives 2 and 3 is generated when setup of HxC is ID0A and ID1B(drive 0 = HxC drive A, drive 1 = HxC drive B).
But drive 0 and 1 operation is no problem.
Ghost drive is assigned a drive letter in MS-DOS, but can not be used in practice.
Of course, no problem in the case where original FDD is used to connect to drives 0 and 1.
The ghost drives 2 and 3 not generated when setup of HxC is ID1A and ID0B(drive 0 = HxC drive B, drive 1 = HxC drive A).
Do you know why ghost drives is generated?
I want to erase the ghost drives using settings ID0A and ID1B the HxC.
I am using HxC SD Emulator rev F with EPSON PC-586RV.
PC-586 is PC-9801 compatible computer, internal FDD is 2 drives (drive 0, 1) and external FDD is 2 drives(drive 2, 3).
PC-586's original internal FDD is EPSON SMD-340 or MITSUMI D353T3.
External FDD is PC-9801 compatible interface, available to PC-9801 general external FDD.
I connected HxC to the drives 0 and 1, and nothing connected drives 2 and 3.(see attached connecting diagram)
The ghost drives 2 and 3 is generated when setup of HxC is ID0A and ID1B(drive 0 = HxC drive A, drive 1 = HxC drive B).
But drive 0 and 1 operation is no problem.
Ghost drive is assigned a drive letter in MS-DOS, but can not be used in practice.
Of course, no problem in the case where original FDD is used to connect to drives 0 and 1.
The ghost drives 2 and 3 not generated when setup of HxC is ID1A and ID0B(drive 0 = HxC drive B, drive 1 = HxC drive A).
Do you know why ghost drives is generated?
I want to erase the ghost drives using settings ID0A and ID1B the HxC.
- Attachments
-
- hxcdiagram.png (39 KiB) Viewed 14503 times
Re: Generated ghost drives problem
Do you have the latest firmware version (1.8.2.40) ?
Re: Generated ghost drives problem
Yes, I use 1.8.2.40.Jeff wrote:Do you have the latest firmware version (1.8.2.40) ?
Re: Generated ghost drives problem
Do you have any idea how the drive detection works on this machine ?ovf wrote:Yes, I use 1.8.2.40.Jeff wrote:Do you have the latest firmware version (1.8.2.40) ?
i think that this is the track 00 checking but can you confirm ?
Re: Generated ghost drives problem
I have a logic analyzer.Jeff wrote:Do you have any idea how the drive detection works on this machine ?ovf wrote:Yes, I use 1.8.2.40.Jeff wrote:Do you have the latest firmware version (1.8.2.40) ?
i think that this is the track 00 checking but can you confirm ?
I am going to try to capture the signal of /ID0 and /ID1, STEP, TRACK00.(if possible, /ID2 and /ID3)
Is there a signal to be captured in the other?
But I don't know take good data, because I don't know the detect timing of the FDD.
For now, I am going to try trigger the timing of TRACK00 becomes LOW.
Re: Generated ghost drives problem
I tried to capture the detect sequence of the FDD.
Detection sequence of this machine seems to be of the following two procedures.
1)move TRACK00
It is output the many STEP pulse to each FDD. Each FDD is moved to TRACK00.
2)Detect drive
It is monitor the status of TRACK00 at the time of the Low level of /ID?.
STEP is not output at this time.
Order to be detected is ID0->/ID1->(probably /ID2->/ID3).
Attach an image captured when I set ID0A-ID1B or ID0B-ID1A to HxC.
I think that there is a problem with the output of TRACK00.
And, DIP-SW to set the ID is poor contact from the beginning of my HxC.
ID0B, ID1B is particularly bad. Is there a way to solve?
Detection sequence of this machine seems to be of the following two procedures.
1)move TRACK00
It is output the many STEP pulse to each FDD. Each FDD is moved to TRACK00.
2)Detect drive
It is monitor the status of TRACK00 at the time of the Low level of /ID?.
STEP is not output at this time.
Order to be detected is ID0->/ID1->(probably /ID2->/ID3).
Attach an image captured when I set ID0A-ID1B or ID0B-ID1A to HxC.
I think that there is a problem with the output of TRACK00.
And, DIP-SW to set the ID is poor contact from the beginning of my HxC.
ID0B, ID1B is particularly bad. Is there a way to solve?
- Attachments
-
- drive_detect_sequence.png (148.99 KiB) Viewed 14463 times
Re: Generated ghost drives problem
Thanks a lot for the sequences.
I had to do a test program to reproduce the issue, but now all seems to be corrected.
I will send you the new firmware once i have done all the tests.
I had to do a test program to reproduce the issue, but now all seems to be corrected.
I will send you the new firmware once i have done all the tests.
Re: Generated ghost drives problem
I received a new firmware, and checked firmware behavior.Jeff wrote:Thanks a lot for the sequences.
I had to do a test program to reproduce the issue, but now all seems to be corrected.
I will send you the new firmware once i have done all the tests.
As a result of the check, I was confirmed that the issue is resolved.
Thank you for helping us make resolve the problem
Re: Generated ghost drives problem
Hi, Jeff
I found the problem in the firmware I got from you.
Reproduce the problem by following these steps:
1st problem
1)Mount the disk on both drives.
2)Unmount the disk in the one of the drives.(push front panel center button)
The other drive disk should remain mounted, but /READY signal becomes H level at all times.
It is same as no disk was mounted on both drives. I think this is problem.
3)If remount the disk that were unmounted, It will be accessible to both drives.
2nd problem
1)Mount the disk on both drives.
2)Switch to other drive.(long push the center button and select drive)
The switching destination drive disk is automatically unmounted. I think this is no problem, but hard to use.
The switching source drive disk should remain mounted, but /READY signal becomes H level. I think this is problem.
3)If mount disk in the switching destination drive, It will be accessible to both drives.
I want to improve the problem because I think two drives is be work independently.
Moreover,I hope that the operation such as the following is realized.
1)The drive is to be switched even if the disk is not mounted. Because may want to mount the disk only drive B.
2)Do not unmount disk when switching the drives
Thanks
I found the problem in the firmware I got from you.
Reproduce the problem by following these steps:
1st problem
1)Mount the disk on both drives.
2)Unmount the disk in the one of the drives.(push front panel center button)
The other drive disk should remain mounted, but /READY signal becomes H level at all times.
It is same as no disk was mounted on both drives. I think this is problem.
3)If remount the disk that were unmounted, It will be accessible to both drives.
2nd problem
1)Mount the disk on both drives.
2)Switch to other drive.(long push the center button and select drive)
The switching destination drive disk is automatically unmounted. I think this is no problem, but hard to use.
The switching source drive disk should remain mounted, but /READY signal becomes H level. I think this is problem.
3)If mount disk in the switching destination drive, It will be accessible to both drives.
I want to improve the problem because I think two drives is be work independently.
Moreover,I hope that the operation such as the following is realized.
1)The drive is to be switched even if the disk is not mounted. Because may want to mount the disk only drive B.
2)Do not unmount disk when switching the drives
Thanks
Re: Generated ghost drives problem
No : all of this is normal : the device cannot emulate any drive while you are browsing the sdcard, that's why both emulate disk are "ejected" at this moment. When you have finished to select your file image, both disks are "reinserted".2)Unmount the disk in the one of the drives.(push front panel center button)
The other drive disk should remain mounted, but /READY signal becomes H level at all times.
It is same as no disk was mounted on both drives. I think this is problem.
If you want a totally independant drive emulation, you should use 2 emulators!
I don't understand.3)If mount disk in the switching destination drive, It will be accessible to both drives.
Re: Generated ghost drives problem
Hi, Jeff
I understood.
I was mistaken to be able to operate two drives independently.
In this state, don't be able to access the both drives.
When reinsert disk in drive A, it be accessible to both drives.
I think it is a normal action in your description.
Thanks
I understood.
I was mistaken to be able to operate two drives independently.
Mount disk in both drive, and switch drive B to A.3)If mount disk in the switching destination drive, It will be accessible to both drives.
I don't understand.
In this state, don't be able to access the both drives.
When reinsert disk in drive A, it be accessible to both drives.
I think it is a normal action in your description.
Thanks