Disk Set Err. 01 = The disk did not set properly.
Battery Err. 02 = The batteries are dead.
Write Protect Err. 03 = The FDS is unable to write to disk.
Game Maker Err. 04 = ?
Game Name Err. 05 = ?
Game Version Err. 06 = ?
A,B Side Err. 07 = The wrong side of the disk inserted.
Disk No Err. 08 = No disk has been inserted.
Disk Trouble Err. 20-29 = Unidentified disk error.
Disk Full Err. 30 = There is no more space left on the disk.
Did I miss any? Help me fill in the blanks.
Game Maker Err. 04 = ?
Game Name Err. 05 = ?
Game Version Err. 06 = ?
4 and 5 are I think when you get a bad pirate port. 6 is when you get a game that needs to be updated and hasn't been, I THINK. I'm not too sure though.
What's Err 40? I got that when resetting a game (after hacking the crap out of it).
Error 40 = Please stop hacking our fucking games. :)
ERROR.01 No disk card
ERROR.02 No disk power supply
ERROR.03 Broken prong on disk card
ERROR.04 Wrong maker ID
ERROR.05 Wrong game name
ERROR.06 Wrong version name
ERROR.07 A,B SIDE ERR.07 Side number wrong
ERROR.08 Disk #1 wrong
ERROR.09 Disk #2 wrong
ERROR.10 Disk #3 wrong
ERROR.20 ‹-"F screen data differs
ERROR.21 Disk header block(*NINTENDO-HVC*)part is wrong
ERROR.22 Disk header block reecognition isn't read and can ignores
ERROR.23 File recognition block can't read for several reasons and can ignores
ERROR.24 File header block recognition can't read and can ignore
ERROR.25 File data block recognition can't read and can ignore
ERROR.26 Can't save properly to disk card
ERROR.27 Block end mark seen and ends prematurely
ERROR.28,ERR.29 The disk unit and the same period can't take it.
ERROR.30 Disk card too full to save.
ERROR.31 Data number of a disk card doesn't match up.
ERROR.40 Go Rutgers!
-CFB
The UNDEFEATED Rutgers. ;)
Hahaha, lol.
Thanks for the list, CFB. :) I'll use it to update the list we've already got at FW.
Quote from: chimyfolkbutter on November 16, 2006, 07:56:48 pm
ERROR.01 No disk card
ERROR.02 No disk power supply
ERROR.03 Broken prong on disk card
ERROR.04 Wrong maker ID
ERROR.05 Wrong game name
ERROR.06 Wrong version name
ERROR.07 A,B SIDE ERR.07 Side number wrong
ERROR.08 Disk #1 wrong
ERROR.09 Disk #2 wrong
ERROR.10 Disk #3 wrong
ERROR.20 ‹-"F screen data differs
ERROR.21 Disk header block(*NINTENDO-HVC*)part is wrong
ERROR.22 Disk header block reecognition isn't read and can ignores
ERROR.23 File recognition block can't read for several reasons and can ignores
ERROR.24 File header block recognition can't read and can ignore
ERROR.25 File data block recognition can't read and can ignore
ERROR.26 Can't save properly to disk card
ERROR.27 Block end mark seen and ends prematurely
ERROR.28,ERR.29 The disk unit and the same period can't take it.
ERROR.30 Disk card too full to save.
ERROR.31 Data number of a disk card doesn't match up.
ERROR.40 Go Rutgers!
-CFB
These are correct, but better wording may be:
Error 3 - Disk is write protected
Error 28 - File ends prematurely during read
Error 29 - File ends prematurely during write
Error 31 - File count in header and number of files on disk do not match
Thanks, madman! :D And welcome!
Welcome!
Thanks guys!
Disk System errors list updated. Thanks CFB and madman! :)
My copy of Metroid arrived today but gives me Error 21.
According to the Disk Error thread, that would be
ERROR.21 Disk header block(*NINTENDO-HVC*)part is wrong
What does this mean? Is there anything I can do to fix it?
Quote from: satoshi_matrix on January 17, 2008, 12:08:28 pm
What does this mean? Is there anything I can do to fix it?
The very first thing on the very first block of an FDS disk is the string *NINTENDO-HVC*. If something other than *NINTENDO-HVC* is found, you'll get that error. So, that's your problem.
I'm guessing that means one of two things. Either, one, your disk is corrupt and won't work. Or, two, your disk is fine, but your FDS is unable to properly read the disk. In either case, I have no idea how to fix it...
I have version 2 disk system that was apparently brand new and never used when I bought it. As for if this was true I can't say for certain but it sure seemed like it.
All of my other disk system games (Doki Doki Panic, Super Mario Bros. 2, Famicom Detective Club etc) all work perfectly and never give errors.
I have a copy of Metroid that gives me disk error 23, which I determined meant that the disk is defective. This copy seems to only give error 21.
does anyone know of any way at all to get Metroid to work? This is quite upsetting as the reason I bought a second copy of Metroid was to replace the version I knew didn't work. So now I'm stuck with two copies that dont work of the same game?
Both of your disks probably work. It is almost never the disk.
I would recommend adjusting the speed of your FDS motor and the spindle mechanism.
This will explain how to adjust the spindle (and replace a belt) http://jfgoods.net/disksystem.html
Thanks kite, I completely read that, but I don't need to replace the belt. I don't see any mention of adjusting the speed of the FDS motor and spindle mechanism anywhere in the article. Could you please direct me to how I should fix the problem I'm having? If it matters, I have a standard Disk System, not a Twin Famicom.
Edit: I notice the page states,
"If you have any rattle or motor noise when you insert the disk in the disk system and a error occurs,
there is a possibility that your belt is worn out."
My FDS makes plenty of noise, similer to the disk drive of my Commodore 64. Is it abnormal for the FDS drvie to make noise? Is the disk read process suppose to be silent? Now this is making me wonder if I do infact have a bad belt. But if that's the case, how come everything else I have will run flawlessly?
I took my disk system apart to check the belt, and it's completely fine - it looks brand new. But now that its reassembled, the newest copy of Metroid gives error 22 consistantly instead of 21. Doki Doki Panic Akumajou Dracula and all of my other disks still work correctly. I want to do the thing where I adjust the motor like Kite suggested. Is there already a guide to this on Famicom World and if not, could someone please explain how to do this? I didn't see anything that looked like a speed selector when I had my drive apart.
On the page, though it does talk about replacing the belt, you need to do the spindle as well, though if the other disks are working I bet you the problem is the motor. To adjust the motor look for the motor, it's on the drive. There should be a small hole with some rubber inside, underneath that rubber is a screw. The rubber is there to discourage you from messing with it I guess, but stick a small flathead in there and turn it ever so slightly until you find a speed where everything works.
99% chance that's your problem
Thanks kite. I didnt really touch the spindle because I didn't unscrew it, I checked the belt out and its perfectly fine. You think there could be a problem with the spindle?
and regarding the motor, its the big silver round thing with the blue sticker on it right? Hmm I tried moving it but it doesn't seem to make any difference. I'm stumped.
Um, You have to leave the top off and turn it a bit then test, turn it a bit then test, over and over again
How sensitive does it need to be? I've tried moving it into at least eight different positions from extreme left to extreme right and still neither Metroid works.
its very sensitive, there's probably like 50-100 different positions. also make sure that you are feeling resistance and have actually made contact with the screw
Okay, I've pretty much adjusted the motor to be almost any position there is within a milimeter.The scre had been moved and moved, but still neither Metroid works. All of my other disks work no matter what speed I set it to. Becides the motor or the belt which I've throughly examined its fine, is there anything else that could be wrong?
I bought Metroid from toysonlinehk and this is what he had to say (slightly reworded to make up for his broken English)
"We had tested the game as fullt working with 2 disk systems before we shipped it out. You can try a few more times first before you return it for exchange. Most disks that won't play don't becase of reasons outside of the disk and with the console itself. You may have a dirty disk head with your machine . if it still won't work , let me know , I can arrnage another one for you."
What is the "disk head" that he's taking about? Maybe it is dirty? If so, how do I go about cleaning it? It's very frustating to have a system that I know works but won't respond with the one game I really want to play.
cool metroid disk system commerical I saw while trying to loko for a solution...
http://www.youtube.com/watch?v=z7sTNJ5sxuk
Um, for the most part the rest of your games should NOT work at every speed if you are adjusting the screw you are supposed to be adjusting. Just to confirm, you're turning the rubber screw in that's inside the thing with the blue sticker on top?
Well if that doesn't work, go to the website I linked and follow the steps starting with
"Here comes the most important part.
First, slide the head so you will get a view like shown on the left."
This will show you how to do the spindle alignment, which could also be your problem.
The "head" he is talking about is the thing that reads the disks, it pops up when you take a disk out and it goes down when you put a disk in. There is an official disk cleaning set, which I have. If it was used I would mail it to you so you could try it but sadly it's sealed and I'm not willing to open it considering it was not easy to find.
Lastly, it could be the disk itself. I think you should try the other things first though.
Another thing you can do is send me the game and I will test it on both my drives (FDS and Twin Famicom) and see if it works, if it doesn't then at least you know. But this would not make much sense since you are from Canada it would cost too much to do
I had reply your message on ebay the same day you send me .
but you never responds . if your metroid don't work after you clean your system . you can email me , I will replacment another one for you .
Hi all,
I know this has been covered loads of times in these forums, but I'm having problems finding a solution which works for me.
I recently got a Disk System and as it needed one, I installed a new belt. I've followed the instructions at http://jfgoods.net/disksystem.html (http://jfgoods.net/disksystem.html) to calibrate the motor speed and also align the spindle correctly, and yet after all that, I'm still getting error 22 all the time. Occassionaly I'll get error 22 once in a while if I've just slightly altered the motor speed, but then I'll be back to 22 again. I have plenty of disks (all originals) and I have the same result for all of them.
Does anyone know of anything I may have missed in order to get this thing up and running?
Thanks any help,
shroomism
this is exactly my problem. 22 over and over and over. speed adjustment doesnt seem to matter.
I just received my lot of 50-some disk games and am getting errors 20, 22, & 27 with a handful of them. All of the games are on non-original nintendo disks--you know, those NINIENDO blue & yellow disks or black or white-colored disks. Any of these errors easy fixes? My disk system works great with all of my other disks so I don't think it's the system.
I just got a doki doki panic pirate disk, and I'm getting Error 27.
Is the disk Bad, because I really wanted to play it :(
I've gotten some of my disks that were giving me errors to work by taking the disk apart and wiping the actual disk from the center toward the outer edge with a soft cotton cloth the whole way around--much like you'd wipe a cd. The disks come apart pretty easily--just gently arc them on the long edge first and then all the way around and insert a thin knife edge into the edge and gently pop the disk apart. Don't force anything, it will come apart with patience. ;)
How would I put it together? Its a pirate disk made of cheap-looking plastic. It could break :-\
All of my disks snap back together--you're basically just gently snapping it apart. Think Legos here :P
If when you snap it back together, it doesn't hold, a little drop of superglue on the inside will do the trick--it'll be easy to see where it should go once the casing is open. I've only opened pirate disks (no original's yet), multiple kinds, and haven't broken one yet. They seem more resilient than the cartridges. ;)
Tried it, but it didn't work :(
What If I use water, will that harm it?
I wouldn't use water. What does the disk look like? Pic?
[Removed]
Picture of disk.
I've taken apart a few of this type. When you bend/arc the disk, do it until it makes a 'pop' or 'snap' on all four sides--use more caution on the side with the disk reader opening. You should see that one of the edges is opened a little bit--insert the knife edge there and gently pop the disk apart. I used a paring knife since it has a somewhat thin & flexible blade.
I used the knife that it is leaning against :P
Still no luck, though :(
If you absolutely can't get it apart, you can try wiping it with a q-tip through the opening. You can rotate the disk with your fingers until you wipe the whole thing. These are the only ways I've ever gotten disks to work, but maybe someone else has a better idea. The disks can be a real pain in the ass. :-\
I've gotten it apart, and wiped it off, and tried again just now, but It still give me error 27.
If I were to make a fdsloadr cable, would I still be able to rewrite it, or would the disk just not work?
Of all the disks that I can't get to work--all but one of them is that same type of black disk. It'd be my guess that they de-magnetize/fail quite often. Any chance your seller would refund you the $ or send you a new disk?
I broke one of my disks already man.......this sucks ass!!!
Yep, disks suck. Never know when they're gonna stop working. I figure in about 10 years or so, none of them will work...just like old computer floppy disks.
How'd you break your disk?
It's official for me --
The Disk System sucks big balls.
Huge mammoth balls,
And sucks them hard.
Error this and error that...
...I'm glad it failed. (http://i52.photobucket.com/albums/g2/jerahcordova/FU.gif)
...
FUCK
Kid Icarus error 27 fuck.
I got so mad at it that I threw it at a wall. The disk sides then came apart.
I've found that with error 27, if you can get to the screen where you choose a saved game, if you delete all the saved games, the disk will work okay again. If you get this error before you get to that screen, your disk is probably shit. Error 27 is 'block end mark seen but ends prematurely'.
I always hold my breath when I load a FDS game, 'cuz you never know when that fuckin' belt is gonna snap or an error code is gonna pop up.
Why isn't FDSLoadr a solution? ???
(I don't have a FDS so I never had much interest in it - I wanna know why it didn't take off among FDS fans)
There aren't really any detailed instructions for it.
The kind with close, high quality pictures, and red circles.
Also I'm a child.
I was looking through my DDP instruction booklet, and I noticed it had a chart that told what all the BIOS errors meant. Could someone give me an English list of these?
Is this what you're looking for?:
http://www.famicomworld.com/Disk_System/Error_Messages.htm
Yes, actually...
Thanks alot eric! :D
EDIT** lol how would you get error 2?
QuoteErr. 02 = No disk power supply -- batteries and/or AC adaptor.
or error 30
QuoteErr. 30 = No space left on disk card (full).
I swear..some of the things Nintendo of Japan thinks of :P
Quote from: 133MHz on July 21, 2008, 11:14:49 pm
(I don't have a FDS
Hm?
Quote from: popibros1 on December 30, 2008, 04:56:39 pm
Quote from: nintendodork on December 30, 2008, 04:51:51 pm
BUMP
So I take it 133MHz still doesn't have the FDS :-/
no he has it.
plus he knows how to write disks..
but give him time to make a thread about it...k?
HMMMMMMM?
It is the Battery error meaning it isn't getting current from the AC or Batteries.
I've tried brand new C batteries as well as an AC adaptor. I've pulled the board out and hooked everything back in.
Still get the same error. The board doesn't appear to have been burnt or anything; the system is just not getting power.
Any ideas?
Thanks!
You have to distinguish between the disk drive not getting power and the good battery signal not being generated.
Both of them cause ERR. 02 by different reasons.
How can you even get Error 2? If there's no current going through the FDS, how can it power on and tell you there's an error?
Quote from: nintendodork on January 23, 2009, 10:46:16 am
How can you even get Error 2? If there's no current going through the FDS, how can it power on and tell you there's an error?
Because the error comes from the RAM adaptor presumably. Which is in the FC, which does have power.
Quote from: 133MHz on January 23, 2009, 10:44:52 am
You have to distinguish between the disk drive not getting power and the good battery signal not being generated.
Both of them cause ERR. 02 by different reasons.
How would I go about doing that? What are my options?
Thanks
EDIT: Removed double post. --JC
Oh, so it turns on through the FC..
I get it.
How do you even erase FDS saves?
A magnet?
Perhaps that's not even a funny suggestion 'cause someone might take it serious. Each game's erase function may be slightly different. Some games give you the option to kill your save. Some, like Doki Doki Panic, don't have an erase feature.
But you can erase the save without harming the disk on DDP
Allegedly. I've never gotten it to erase.
http://www.famicomworld.com/forum/index.php?topic=849.0
I've erased the saves on all 7 disks that I have had. (of Doki Doki Panic)
EDIT: Third time, now. Please press Reply instead of Quote. --JC
EDIT: Every other board I use does it one way; apparently this one breaks convention. --Carl
EDIT: JC especially made a new nice reply button. --manuel
That just seems dicey to me. FDS games are prone to self destruct on their own, no need for me to encourage it. Besides, there's no advantage to erasing DDP. There's nothing stopping you from playing through the game as each character again, and nothing will be different. My copy came fully beaten, and I just like to hop around at complete random.
Well, I would want to erase it to try to beat it from scratch myself, with ability to just ship the hard chapters. Regardless, I guess, it don't erase for me, so I get to jump ahead anyway.
So I guess there's no official answer to erasing Disk saves. The only thing I can offer is using a Disk Writer and re-writing the game if the game is on the Disk writer but I don't know if Doki Doki Panic is.
There aren't any Disk Writers available for writing. But, you're right that you could demagnetize the disk to erase and then rewrite the game -- though the ROM might have unerased saves.
wont load on the second side >:( says err 27 ive seen some post that state this is a tuning issue but other that say its a bad disk . i got it from the famicom shop whats there return polisy? ???
You better ask the shop yourself instead of us for the return policy. ;)
Error 27 is"Block end mark seen but ends prematurely." I had a few disks that did that. Try deleting the saved players (games) on the disk. This allowed me to use the disks after I setup a new player 'account'.
Try very genty rubbing the actual disk part with a qtip, or shaking it. That's what I usually do :|
Shaking is what I do, too. ;D But I'm not sure why that helps. And it doesn't most of the time. :'(
I got really mad at Kid Icarus disk, so I threw it down the stairs at a wood floor.
Then it worked.
But don't do that.
We Germans do that all the time. Use brute force to repair stuff.
TV won't work? Slap it hard and it's ok again. Works often for me. :D
to get to the saved games you have to load side b :-[
Quote from: jimhmphry on February 09, 2009, 05:40:41 pm
wont load on the second side >:( says err 27 ive seen some post that state this is a tuning issue but other that say its a bad disk . i got it from the famicom shop whats there return polisy? ???
You can read our return policy here:
https://famicomshop.com/shipreturns
As far as error 27, that usually means your FDS motor needs tuning. It is likely reading the disks too slowly and the motor needs adjusting. Error 22 usually means the opposite, meaning the disks are read too fast.
I did test the disk before it left here and it worked fine.
Please PM me or email me at carl@famicomshop.com with any issues.
Thanks,
Carl
clock wise or counter clock wise ???
You'd want it to read a bit faster, so counter clockwise. Even the most minute adjustments can make a difference.
If you still have trouble with it after adjusting your motor, feel free to send it back and I'll replace it.
But be patient as adjusting the motor takes some time.
Thanks,
Carl
Quote from: manuel on February 09, 2009, 05:51:24 pm
We Germans do that all the time. Use brute force to repair stuff.
TV won't work? Slap it hard and it's ok again. Works often for me. :D
Hey I always smack my cellphone for it to work god the LCD once turned off so I threw it from the stairs and bam! worked like a charm! woot!
Maybe you got some German heritage in you. ;D
WAAAAAAAHHHHHHHHHHHHH!!
Quote from: FamicomFreak on February 10, 2009, 10:17:24 pm
Hey I always smack my cellphone for it to work god the LCD once turned off so I threw it from the stairs and bam! worked like a charm! woot!
My cellphone's screen went kaput once too...
I threw it...didn't work..so I got another one for free from the company ;D
Smacking the hell out of electronics reseats broken/cold solder joints, that's why it works and it's a legitimate diagnostic tool.
I guess you've never seen TV/PC monitor repair technicians at work. The first thing they do when they get a unit with a weird problem is beating the hell out of it :P.
The first TV I had to myself was this old console TV, the kind that ran on tubes. I used to instep kick the side of it to stabilize the picture so I could play NES. Probably reseated the tubes. Eventually though, no amount of brute force could keep that thing going. Later we had a somewhat newer TV in our basement that I played on. Newer as in no tubes, but it did still have a fine tuning control. This one would tint heavily green until you gave it a good whack.
:'(
Hi all, I am new to new website. Though i am encountering a massive problem with my FDS drive.
Recently acquired a FDS drive which was promised in working order after changing the belt, in which i did do.
Though I am getting msg Error 22 which says the disk drive is not performing.
Can anyone kindly give me some hints of whats going on>
hi there, exactly the same as me then, i bought an FDS and after replacing the belt all i get are error 22 messages.
the only thing i've found so far is a guide to adjusting the drive head
http://homepage.mac.com/triumshockwave/random/fdsheadtuning.pdf
you'll need a micrometer caliper though, i've haven't been able to borrow one so haven't tried this yet.
good luck!
sorry if i should post this in tech.... im new here.....
I have a fds that i replaced the belt on... After replacing the belt and adjusting the motor speed a little i was able to get some of my games to run.... The other ones return error 27! Im almost 100% sure the motor speed it right and i have not messed with the head alignment since im scared to mess something up... Im unsure of its the game causing the error but i doubt thats the case... I was able to get some of the error 27 discs to boot up once or twice but not consistantly.... Im pretty sure the grub screw is in the right spot and everything sounds good when reading discs that work... i need help.
Thanks in advance guys...
You'll probably need to adjust the spindle positioning. First try cleaning the read head with isopropyl alcohol and see if that clears it up.
Due to the way the drive is setup, replacing the belt inevitably messes with the position of the spindle that turns the disk. It needs to be in a fairly accurate position since it determines where the drive starts to read disk data.
When adjusting it, use very small increments and re-test after each.
i tried cleaning it but didnt try adjusting the head.... some games work some return error 27.... how do i adjust the head... just turn the small screw loacated in the drive with the redish glue...??? how much do i turn it and in what direction?
Check your PMs. Don't adjust any screws with wax or red glue on them! :o
thanks eric for your help. i was able to get it working by adjusting the grub screw a tad to the left.... Without your help i wouldnt have been able to get this running at 100%.... its people like you that keep me motivated in trying to do it myself.... Thanks again
Glad I could help you out! ;)
Hope you stick around here awhile. There's an "Introduce yourself" thread under the Off-Topic Chat category if you're interested.
Quote from: ckenda1 on January 23, 2009, 10:43:09 am
It is the Battery error meaning it isn't getting current from the AC or Batteries.
I've tried brand new C batteries as well as an AC adaptor. I've pulled the board out and hooked everything back in.
Still get the same error. The board doesn't appear to have been burnt or anything; the system is just not getting power.
Same problem for me. RAM adaptor works like a charm with FDS loader, but when I plug it on the FDS drive I have an error 2. With or without disk in drive. The loading screen comes up immediately after RAM adapter is plugged to drive and quickly after I have error 2. Sometime it loads "something" but nothing happen, the drive load in loop and ejecting disk don't stop the motor.
I would say that, given that description, you have a damaged or broken switch on the analogue board; probably the
head-return switch. Alternatively, the head wire may be hitting the battery tray, preventing it from fully-engaging the switch. :bomb:
FDS Error Code Translations (by Flashback V.E. (http://www.atariusa.com))00-and-10-Codes: These are drive start-up problems.
Err.01: The disk card is not fully seated. Your card-carrier tray may not be entirely engaging, and may be missing sprigs, or require cleaning, etc..
.
Err.02: Power not coming through; battery box not wired, or Power Board board not energized, or drive mech not properly connected to Power Board. Occasionally, this can also be caused by the belt slipping off the motor pulley as well; or by use of an improper or worn belt or band in its place.
Err.03: Disk is write-protected.
Err.04: (Anti-piracy) File mismatch (manufacturer ID)
Err.05: (Anti-piracy) File mismatch (game title ID)
Err.06: (Anti-piracy) File mismatch (game version ID)*
*I had problems with two 'Hikari Shinwa: Palthena no Kagami' disks. I had overwritten the front side of my primary, original game disk (that had my excellent game save files on the reverse) with that of a bad disk; I was trying to do the reverse (restoringthe bad disk with my good one), and I ended up corrupting Side-A. I figured it was no problem, and wrote both from a third copy, and then all hell opened up, as my original disk was V1.0 (or something like that) and the third disk was a later version (e.g. V1.1).
The front would load, and when I flipped it over, it became an error-nightmare because of a version mismatch. In the end, I had to wipe my save files and restore the disks from the third copy. Lesson-learned: Do not use half-a-disk for a backup! Always back up both sides (or all four, for multi-disk games)!Err.07: You have inserted a disk that is either blank, or is the B, C or D side of a multi-disk game. Eject it and flip it over. For multi-disk games, check to see what side you should be using. if the other side of your disk is a single-sided game, such as 'Super Mario bros.', then its reverse (giving the Err.07) is blank.
Err.08: Similar to Err.01. No disk in drive, but insertion switch is engaging; possibly also disk not fully seated. Switch may be damaged.
Err.09: ?? Not disk No.2?
Err.10: ?? Not disk No.3?
Err.11?: ?? Not disk No.4?
Err.12-19: I don't think these exist, but it is possible. I may check a dis-assembly of the FDS BIOS for them sometime.
20-Codes: These have to do with properly reading data from disks.
Err.20'Screen data differs'; I am not sure about this error, or its description. I presume it is actually a
block error of some kind, based on how it is categorized numerically.
Err.21: Index Spindle<-->Motor and other calibrations off. Drive cannot read initial disk header file.
Err.22: Flow of data is not correct, or is simply not happening*. Data may be garbled, or out of sequence, etc.. This can be caused by:
- Improper Index Spindle & Motor calibration
- A bad (or dirty, or not connected) Read Head
- The Analogue Board switches not engaging, or not engaging correctly.
- A mis-seated Disk Card
- A blank A-Side disk, or a blank disk in general.
- A dead disk...or a Game Doctor Disk!**
- A disk with MIDI sequences on it, or word processor files.
- The belt slipping off the motor pulley; or a bad, worn or improper belt or band.
- Possibly other things...
*Essentially, this means that the lights are on, but no-one is home. The FDS senses a disk in the drive, but can' make any sense of the data on it. If there is a problem with the Read-head assembly, then the drive may also think the same thing, as it is trying to read a disk and it can't make any sense of the data because it sees nothing.
*Game Doctor Disks may give this error if you do not have the correct GD attachment. They will assuredly give an error of this type if you try to read them without a GD device, although other errors are also possible in this situation. This is common for pirate disks out of China.
Err.23: Similar to Err.22 in terms of index spindle-alignment. This is a problem with the index-spindle & motor calibrations and occasionally means you are closer to proper alignment, although this is not always the case.
Err.24: Disk media is damaged. (This is the only way I have ever seen this!)
Err.25: Disk media problems?
Err.26: Disk media is probably damaged. I see this almost entirely when reading from or writing to disks with a dimple or bend in the Mylar. It is also an error when writing to a disk using a 3206 drive, or with a PWR-03 or later) Power Board; essentially, the drive throws an error due to the copy protection. If you have a later drive with the write-protection circuitry, you will likely see this error quite often if you try copying disks.
Err.27: Index Spindle<-->Motor and other calibrations off. Drive cannot read initial disk header file.
Err.28: Similar to Err.22 and Err.28 calibration problems. Usually, this means you are closer to proper alignment, but this is not always the case.
Err.29: Spindle-alignment problems?
30-Codes: These are regarding disk file problems, reading and writing.
Err.30: Disk is full; cannot save.
Err.31: The number of files on the disk does not match the declared (expected*) number of files.
*This is another anti-piracy measure: There is an index file with game declared number of files that should be on the disk. When reading the data, if the number of files on the disk does not match the declared number of files then the programme throws an error message; possibly with in-game 'Don't Pirate Me.' text..
Err.32-39: I don't think these exist, but it is possible. I may check a dis-assembly of the FDS BIOS for them sometime.
Err.40: I don't recall off-hand, but it may be noted in my book. I think it is 'Disk data still in memory.', or something along that line. :bomb:
Just to add to your nice post, err.02 also means the motor is being slowed down by a wrong/old belt and thus reporting a power failure error
i wanted to make this my 1,000th post, but No. 999, or something like that was clos enough. I had a post or two post deleted when an author deleted his thread, which dropped this down just as I was writing it.... I had intended it to be a special 'Post-1,000' revelation.
Now that you mention it, yes, both Err.02 and Err.22 can both be caused by belt slippage. I'll edit the original post to add these. :star:
@ Mods: This thread should be moved to the Tech Topics board and stickied, if you please, unless you prefer that I re-post my list there and then you can simply sticky that, ensuring it is at the top of the thread. :bomb:.
P.S. I posted a thread int he tech area, with the details on my post in this thread. Please sticky that... I think that this thread has too much clutter to go over there, and I am willing to either delete my post in this thread, or leave it alone, at the discretion of the mods.
Quote from: Doc on November 17, 2006, 08:17:46 am
The UNDEFEATED Rutgers. ;)
Hahaha, lol.
It is hard to imagine that Rutgers would go undefeated through 9 games today. Although, this year wasn't so bad I suppose.
Also, need help with Error 21 and 22.
You have a spindle index + motor calibration problem. I think I covered this for you in another thread, and would request that you please keep technical help requests to the tech support boards, and I also suggest trying the search feature, as this topic has been discussed many times, which is why some of us aren't answering you in detail. :bomb: