Ignoring erroneous error on boot up.

[r0jaws]

Its a minor niggle, but one I haven't been able to work out how to fix.

On boot, my 1200 shows a 'bad number' error before continuing with its boot as normal.

I know why this is, I have a PrismII based network card and that set up string is in my User-Startup sequence.

Because I have used WEP encryption and entered my full 26 digit long encryption key, i get this annoying little error on start.

It all functions as it should apart from this error.

Therefore, my question is this; does anyone know what I have to enter into my User-Startup to tell my miggy not to display this error?

I have dug through my AmigaDos manual and haven't found anything that helps.

Anyone have a clue?

[DH]

Not sure mate, but I think you can use the 'quiet' command to stop the error from displaying on screen. That's if you have it in your C directory, if you don't you'll need to get it from somewhere

[Graham Humphrey]

You could always try tacking on a '>NIL:' at the end of the command which should stop it displaying the output, whether it would make a difference for your problem I don't know.

[thomas]

Because I have used WEP encryption and entered my full 26 digit long encryption key, i get this annoying little error on start.

It all functions as it should apart from this error.

I doubt that WEP works correctly if the command throws an error message. You should correct the command or remove it completely.

>NIL: will suppress the error message, but it will not make the command work better.

[r0jaws]

Thanks Gents, adding >NIL: to the end worked a treat.

@Thomas, I know it seems odd, given that it produces an error, but the wireless connection works flawlessly.
I am typing this on my 1200 as we speak, the connection is strong & reliable.
It could possibly be a bug that makes it throw up an error message where no problem appears to exist.
I am no programmer and have no idea, but that seems logical, if it reports an error that seems to have no impact on functionality.

[thomas]

I'd rather suppose that your WLAN connection runs without any encryprion.

Or perhaps you didn't correctly identify the command which causes this message. Perhaps it's another one.

[r0jaws]

It is a bit odd,
definitely running encryption on my network, Purposely downgraded it from WPA to WEP for the miggy with MAC addressing as an extra.
This is on my Lappy and I have just checked on the wireless settings that it is security enabled, which it is.
I also tried to connect with a my daughters lappy without the WEP details entered and it got nowhere.

The error disappears when I semi colon out the PrismII setup line and re-appears when I delete the semi colon so its definitely that line.

I know others who have set up wireless via the prismII have used shorter WEP encryption keys and I found no reference to this 'bad number' error linked to prism devices anywhere on Google.

I would have thought it may have been a more common error, but apparently not.

[DoogUK]

I'm using WEP 64bit on the ma401 and dont get an error message.

[r0jaws]

I'm using WEP 128bit encryption, hence the 26 digit entry causing the error I suspect.

64bit produces only a 10 digit string does it not?

[thomas]

I have done a few tests with SetPrism2Defaults and I tell you that either your key is too short (less than 26 digits) or contains invalid characters (only 0-9 and a-f are allowed). It does not complain if if the key is too long.

And I am sure that the erroneous key is not used. It should even stop executing the startup-script because it sets return code 20 (unless it is run after a failat 21).

[DoogUK]

Originally Posted by r0jaws

I'm using WEP 128bit encryption, hence the 26 digit entry causing the error I suspect.

64bit produces only a 10 digit string does it not?

Yes.

Thats normaly secure enough if using mac address filtering as well but i wouldn't recommend it without as wep 64 bit can be cracked in a matter of seconds.

[r0jaws]

I have just recounted and checked the WEP key and every single entry is alphanumeric and there are definitely 26 characters.

Could it possibly be because the I have used Caps rather than lower case?

I'm just backing up the drive, will check shortly.

[Edit] Nope that wasn't it either [/EDIT]

Just so there's no confusion here's my User-Startup

;ClassicWB User-Startup

C:Anticlick

Assign A-Games: SYS:Games
Assign A-Temp: SYS:Temp
Assign A-Programs: SYS:Programs
Assign A-MyFiles: SYS:MyFiles
Assign A-Demos: DATA:Games

Assign Scalos: SYS:Expansion/Scalos
Assign JPEGTMP: SYS:T
Assign AWEB_APL: A-Programs:AWeb_APL

;BEGIN MUI
if exists Sys:Expansion/MUI
assign MUI: Sys:Expansion/MUI
if exists MUI:Libs
assign add LIBS: MUI:Libs
endif
if exists MUI:Locale
assign add LOCALE: MUI:Locale
endif
version >nil: exec.library 39
if not warn
if exists MUIocs
if exists HELP:dummy
endif
assign add HELP: MUIocs
endif
endif
endif
;END MUI

C:Mount KCON: from DEVS:KingCON-mountlist
C:Mount KRAW: from DEVS:KingCON-mountlist

SYS:System/Rexxmast >NIL:

C:xfdPatch >NIL:

Run >NIL: C:XpkMasterPrefs

C:CAPrefs >NIL:

Assign Miami: DH0:

C:CardReset

SetPrism2Defaults SSID SKY12345 KEY a123abc123a1a1234a12a1a1a1 Channel 01

;BEGIN CacheCDFS
;END CacheCDFS
;BEGIN MountLS120
;END MountLS120
;BEGIN ActivateCrossIDEfix
ActivateCrossIDEfix ALL
;END ActivateCrossIDEfix

Only changed the alphanumerics but that is the correct sequence of numbers/ letters.

[Zetr0]

@r0jaws

it might be an idea to get snoop-dos running on startup in the background.

[thomas]

SetPrism2Defaults SSID SKY12345 KEY a123abc123a1a1234a12a1a1a1 Channel 01

Channel 1 is invalid. It only accepts Channels 3 through 14. The key is not the problem.

[r0jaws]

Ok, thanks for pointing that out.

The router from Sky is set up with channel 1 as default.
Is there any particular reason why the prismII doesn't accept channels 1 & 2?

If that is the problem then I shall just leave the >NIL: command in. I have numerous wireless devices and there would be no point in changing all their settings when a simple command on the miggy sorts the problem.

Thanks for the inputs guys, the error no longer bother me, therefore, I'm happy.