Hi everyone!
i'm having an issue that's screwing with my brain.
A friend of mine rewrited me some Famicom Disks using FDSLoadr, a DOS computer and the right cable. We tested the games with my console (a Famicom AV) and his Disk System, the games worked fine.
Back home, i plugged my famicom av to my disk system and the 4 games gave me the same error 22. We have absolutely no idea of what's causing this.
Furthermore, all of my original games work fine. So I'm turning to you for help.
Hope someone will have some ideas or answers...
Thanks!
Did you copy it using a game doctor?
Try tuning the motor speed.
Helped me when i kept getting err. 27. There's a game doctor disk that helps you tune your disk system too.
I didnt either... I was just trying to offer advice! Don't get mad.
I suspect 80sFreak has insomnia. :D
Quote from: 80sFREAK on August 12, 2012, 04:28:54 pm
Quote from: fredJ on August 12, 2012, 12:58:15 pm
I suspect 80sFreak has insomnia. :D
Just tired of this sort of "advices".
If you're tired of shitty advice, stop being a smartass and offer up what you know. ;)
I actually had this problem today as well. I was at a bud's house, and his Twin Famicom couldn't read any of the disks I had written on my drive, but all of the original disks we tried worked fine. I'm guessing one of our drives needs calibration.
Sounds like a lot of work!
80sFreak: Don't forget my drive came from you. Guess which FDS I think is the problem? ;)
Yeah, my drive works perfectly with both original and rewritten disks. Bud's drive only works with original disks, but works perfectly on originals. I'm going to try my disks on a third bud's Famicom Twin and see what happens.
To add details, I can say that at my friend's house, both original and rewrited games work. I don't really want to mess with reading calibration as it works fine with original games and I wouldn't want to mess that up.
Does anyone has real ideas on what could be the REAL problem? If I try to write the games using his computer, his cable but MY FDS, will it make the games work on my FDS?
could it have to do with disk system revision?
is this a commons problem? I can't sell disks that give error 22 at random FDS.
thank you mr freak. :)
I wonder , in the disk writer machines, disks were also rewritten and generally work. Maybe err 27 on badly calibrated systems but not err 22 that I've seen.
What is the difference when you rewrite it yourself?
Thanks a lot, 80sFreak!
Then I will try with mine.
I've modded it following the instructions on the site (it's a revision 5) but I don't know how to identify if the reader part is protected or not (as it seems to be 2 versions of it).
May I add that i have another rewritten game (Bubble Bobble on a Kinnikuman disk) that I got along with my FDS and who works perfectly fine.
Is the official Nintendo testing disk the FMC Card Checker or something else?
Post Merge: August 13, 2012, 05:50:24 am
What copy program did your friend rewrite the disks with?
Error 22 in my experience is because the disk media surface isn't touching the read head adequately because of a worn pressure arm pad or the hub is set too high on the spindle. Try applying slight pressure by pressing lightly on the pressure arm while the FDS is trying to read the disk to see if you can get it to read. Clean the magnetic head with isopropyl alcohol while you're in there.
Quote from: ericj on August 13, 2012, 05:41:04 am
Is the official Nintendo testing disk the FMC Card Checker or something else?
Post Merge: August 13, 2012, 05:50:24 am
What copy program did your friend rewrite the disks with?
Error 22 in my experience is because the disk media surface isn't touching the read head adequately because of a worn pressure arm pad or the hub is set too high on the spindle. Try applying slight pressure by pressing lightly on the pressure arm while the FDS is trying to read the disk to see if you can get it to read. Clean the magnetic head with isopropyl alcohol while you're in there.
1) no idea what is that. do you have any manuals for FMC card checker?
2) looks like err.22 is equal to "no signal" and err.27 is equal to "bad CRC"
He used FDSloadr.
I tried the slight pressure and it didn't change anything. I'm a little worried about other things I could try. I'm afraid i'd do something wrong and f**k up the FDS completely.
I'm all aout of ideas and my friend has no clue either on what can cause this problem.
You cannot just use fdsloadr. What copy program did he use?
Do you know if he completely modded his FDS, including the power board? Some of the copy programs don't write the entire disk, so it's best to use Makko's Copy Master since it does, although it requires a game doctor to load,
ericj: What's the best copy program to use if you don't have a copy master? I think the one I've been using was Disk Hacker, it was the only one I could find that was in English and worked through FDSloadr.
I really only ever use Copy Master. I think Disk Keeper is okay, too, but it's too time consuming whereas Copy Master is quick.
Depending on which hacked up version of Disk Hacker you're using, this could be what's causing your problems.
I dont know if he used something else than fdsloadr... He used a program that appeared on the PC screen like this :
(http://i30.photobucket.com/albums/c325/chimyfolkbutter/Diskkeeper/FDSLoadrProgram.jpg)
What he did was :
1/ Fdsloadr loaded on dos -> going to fds ram via special cable
2/ Selecting a rom -> Loading it o fds ram via special cable -> Plugging the FDS with a disk inserted
3/ repeat 2 for the other 32k
4/ same as 2 but for B side
We had to try it many times for all the games we tried, getting either no result or a game filled with graphical glitches.
The it worked for 4 games, that we tried to load on my console with his FDS and it worked.
What I don't understand either is why we had to try so many times when back when he did it for his games (last month) it worked the first time.
I'm really at a loss of ideas, here.
Sounds like he used Disk Keeper. The glitches and problems could be the roms themselves, his disk, or his FDS.
I really don't think so. He seemed to have used only FDSloadr and loaded the roms directly to the ram.
Could it be why it didn't work?
Post Merge: August 16, 2012, 03:38:23 am
Now I remeber! He used Disk Hacker 2 to rewrite the games!
Can the problem come from that?