Hi All,
I've been trying to do a couple disk-to-disk copies on my MGD1 that I finally received from ToToTek,and I'm having some issues in my attempt to do this with the unit as a standalone device. This is the procedure that I'm using:
1 - Attach RAM-Adapter to MGD1 and connect to FDS
2 - Apply power from a wall-adapter to FDS;
3 - Apply power to the MGD1;
4 - Insert a disk to read.
I discovered that running the FDS on batteries does nothing with the MGD1, but on wall-power, it seems to be working...or at least somewhat:
At first, a couple disks gave me spinning segment series, then an Error code. Then, after re-leveling the drive (all FDS hate being off-level and will spew error codes when they are leaning too far in a given direction.), when I start up the MGD1 and insert a disk, I get some status indicators as follows...
When I turn on MGD1, it gives the status light like this:
._
|_|
|_|
When I insert a disk, The MGD1 starts to read and gives status lights that look like:
._
|_|
|_|
or like:
._
|_|
|_|
Do you know what causes this? What is the meaning for these displays?
I don't see any spinning segments, just an endless cycle of reading the disk, the drive clicking, reading the disk, etc. I tried a few disks, including various original Nintendo and Chinese disks, plus an original copy of SMB--and all of the disks fire up and load from this drive normally.
I'm not sure if it has issues with my FDS unit, or what these codes mean. Is there a list of MGD1 codes somewhere, or is this lost in translation?
Maybe there is some copy-protection mechanism still intact in the drive that I missed? I swapped out my modified Rev 3 power board for a Rev 2 that I had in a parts unit FDS, but no soap: It still gives me exactly the same readouts and I haven't a clue what they mean. I'm giving it 2-3 minutes to read the surface of a disk at present, before killing power to the MGD1; is that sufficient?
Can anybody confirm or deny that these codes are due to copy protection in the FDS and not something else?
--or--
Could it be a dirty connection between the RAM-Adapter and the MGD1, or is something horribly wrong???
-Xious
I've been trying to do a couple disk-to-disk copies on my MGD1 that I finally received from ToToTek,and I'm having some issues in my attempt to do this with the unit as a standalone device. This is the procedure that I'm using:
1 - Attach RAM-Adapter to MGD1 and connect to FDS
2 - Apply power from a wall-adapter to FDS;
3 - Apply power to the MGD1;
4 - Insert a disk to read.
I discovered that running the FDS on batteries does nothing with the MGD1, but on wall-power, it seems to be working...or at least somewhat:
At first, a couple disks gave me spinning segment series, then an Error code. Then, after re-leveling the drive (all FDS hate being off-level and will spew error codes when they are leaning too far in a given direction.), when I start up the MGD1 and insert a disk, I get some status indicators as follows...
When I turn on MGD1, it gives the status light like this:
._
|_|
|_|
When I insert a disk, The MGD1 starts to read and gives status lights that look like:
._
|_|
|_|
or like:
._
|_|
|_|
Do you know what causes this? What is the meaning for these displays?
I don't see any spinning segments, just an endless cycle of reading the disk, the drive clicking, reading the disk, etc. I tried a few disks, including various original Nintendo and Chinese disks, plus an original copy of SMB--and all of the disks fire up and load from this drive normally.
I'm not sure if it has issues with my FDS unit, or what these codes mean. Is there a list of MGD1 codes somewhere, or is this lost in translation?
Maybe there is some copy-protection mechanism still intact in the drive that I missed? I swapped out my modified Rev 3 power board for a Rev 2 that I had in a parts unit FDS, but no soap: It still gives me exactly the same readouts and I haven't a clue what they mean. I'm giving it 2-3 minutes to read the surface of a disk at present, before killing power to the MGD1; is that sufficient?
Can anybody confirm or deny that these codes are due to copy protection in the FDS and not something else?
--or--
Could it be a dirty connection between the RAM-Adapter and the MGD1, or is something horribly wrong???
-Xious