"Bad Number"

[MiAmigo]

While its true I am taking some time off from fighting with the A2000, I find that I can not totally put the cryptic message out of my mind which I see at bootup ever since I turned startup-sequence into a tattle-tale:

Bad number

That's it - that's all it says, and nothing more. No identification whatsoever!

So what, pray tell, does this mean? Exactly what is it referring to?

Even though everything seems to be going correctly - with all my drives mounting as they should (something I was sure I would never see in this lifetime!), I still can't help but feel that this message, that seems to refer to everything and nothing, will come back to haunt and vex me in the end!

What the heck its it? A filesystem failure, a corrupt library, a bad .device file, an incorrectly configured mount file? An ex I dumped years ago because she was a bad number?

Well you get the picture!

HALP!
:cry:

[Thomas]

This message comes from a command which requires a number as argument but got something else, for example a letter.

The cause is probably a typo, for example addbuffers df0: fifty instead of addbuffers df0: 50

Put set echo on as the very first command into your startup-sequence. It will then print every command to the shell before it executes it. With the help of this you can find out which command prints the message and correct it.

[MiAmigo]

This message comes from a command which requires a number as argument but got something else, for example a letter.

The cause is probably a typo, for example addbuffers df0: fifty instead of addbuffers df0: 50

Put set echo on as the very first command into your startup-sequence. It will then print every command to the shell before it executes it. With the help of this you can find out which command prints the message and correct it.

Thanks for the tip!! I'll check this out A.S.A.P.!

[MiAmigo]

This message comes from a command which requires a number as argument but got something else, for example a letter.

The cause is probably a typo, for example addbuffers df0: fifty instead of addbuffers df0: 50

Put set echo on as the very first command into your startup-sequence. It will then print every command to the shell before it executes it. With the help of this you can find out which command prints the message and correct it.

AHA! SetPatch QUIET is the culprit! Now, what is the cause? And, equally important - how to fix it??

[MiAmigo]

Now I remember! I had previously installed a BOGUS version of SetPatch when I was trying to make Ami-CDFS work.

I was never able to successfully mount my CD using Amy, so I ditched it in favor of another program (Cache-CDFS), but forgot to remove Amy's version of SetPatch.

As far as I'm concerned, Ami-CDFS is a boondoggle!

Once I restored my original SetPatch, the 'bad number' error vanished. (I guess I'll have to manually go after all the other files Amy asked me to copy over to various system folders while I was installing it, just to be on the safe side.) I wish there was an 'uninstall' program for this type of thing!

I think I rather prefer having Set ECHO On! I can see everything that's going on during bootup. I'll leave it for now.

Question: What, exactly, does SetPatch do?

[Thomas]

I am quite sure that AmiCDFS never asked you to replace existing system files with older versions. The supplied SetPatch is meant for early versions of AmigaOS (2.0 or something). If you already have a newer version you should not replace anything.

[MiAmigo]

I am quite sure that AmiCDFS never asked you to replace existing system files with older versions. The supplied SetPatch is meant for early versions of AmigaOS (2.0 or something). If you already have a newer version you should not replace anything.

It's pretty specific - copy these files here.

The set of instructions I have are dated (of course) and make several assumptions which will get you into trouble if you follow them literally - such as telling you to rename your scsi.device file after the name of your CD device, which means that,unless your actually have a file by that name on your rig, it will not work.

http://cd.textfiles.com/zoom2/help/amicdfs2/amicdfs.guide

[mongo]

The set of instructions I have are dated (of course) and make several assumptions which will get you into trouble if you follow them literally - such as telling you to rename your scsi.device file after the name of your CD device, which means that,unless your actually have a file by that name on your rig, it will not work.

It doesn't tell you to do that.

[Methuselas]

The set of instructions I have are dated (of course) and make several assumptions which will get you into trouble if you follow them literally - such as telling you to rename your scsi.device file after the name of your CD device, which means that,unless your actually have a file by that name on your rig, it will not work.

Yeah, that's not right, at all.