MUI Class "Bug"

[Zadoc]

I took recent notice that I have a 'buggy' MUI class lib somewhere.

The problem being: whenever the word "Elbox" is spelled into a text gadget, string, etc. via any MUI class, it is 'cutely' respelled as "elb*tts", "hellbox", "elbugs", and a few other choice mis-spellings.

Unfortunately, I've copied over my MUI classes recently with a CD backup so the datestring on the files all read the same...

Does anyone have any idea which MUI class has this 'feature' hacked into it, which version it may be?

The joke was sort of cute, but is rapidly becoming annoying...

Thanks

[Zadoc]

After a bit more research, it appears to be affecting non-MUI strings as well...apparently I think this is a virus, no luck on defeating it yet, but if anyone has any info on it I'd be glad to hear about it.

I'll keep everyone posted if I find out anything more, myself.

[Zadoc]

I'm not 100% positive, but it looks to be a Poseidon 'bug'!

Typing out Elbox on my attached A3000 kb through the powertower kb adapter doesn't affect anything.

The same word typed on a kb attached to the USB card causes this 'bug' to emerge...

[lempkee]

wow, aint that VIOLATING THE LAWS ?

wonder if that will format your RDB aswell..

hmm

[Kent]

How to find a virus that isn't already detected by virus scanners.

Step 9: get a new virus scanner.  :-D

No seriously.  Jot down all the programs that you have in your startup sequence.  Run the programs one by one and test each program with a known program that chokes on the strings with "elbox".  When you find the culprit, post the info here.  If you want to post the offending file I'll see what I can do to pick it appart to locate the origin of the devious task.

Good luck!

Edit past this point:

So it works on the shell without launching any programs? (holding down both mouse buttons).  From what I understand of the fight between the author of Posieden and Elbox, this bug stands to reason.  A bit of a low blow if it's coming from the Posieden stack though.

:pint:

[Framiga]

Hi

i think, like Lempkee me too, that is the Elbox "joke" about theyrs " modified" drivers.

It is a well known behaviour :-) . . .mhhh!!! Elbox . .  .bad boys!!!

Ciao

[Zadoc]

After booting with no-startup sequence, trying USB keyboard attached to bootkeyboard.class, this 'behavior' didn't exist.

Adding MUI:LIBS assign, running trident prefs,  and binding the keyboard to HID.class, revealed what I suspected - this is a Poseidon 'bug'.

i think, like Lempkee me too, that is the Elbox "joke" about theyrs " modified" drivers.

Yes, I understand the 'joke' it just frightened me that a 'virus' might have attacked my system!

It is a well known behaviour :-)

If you mean this 'bug' is a well known behavior, it wasn't to me.  I subscribe to the Highway/USB mailing-list and frequent both Amiga.org and ANN.lu and have not heard anyone report this as of yet...

Like I said, I understand the 'humor' but I just think this was a little scary due to all the anti-Elbox attitudes held by most.

Honestly, I think it's believable anyone could have 'hacked' out a virus that'd do something like this...and possibly worse that'd remain unnoticed...

I'm relieved that it isn't a 'virus' but I do find it in slight of poor taste after I have spent a good two hours virus checking my harddrive!

mhhh!!! Elbox . . .bad boys!!!

Perhaps...but sometimes Chris Hodges behavior is a bit bizarre in return.

[lempkee]

zadoc:thanx for info..

i dont like the idea of this , remeber this is how everything started in the first place (elbox put hidden code in spider software (for anti crack/hacking reasons)

[Framiga]

Hi Zadic,

it isn't a "virus" perse but one of the bizarre protections made by Elbox for one of theyr products.

I don't know, why all that is happened on your system but i know, as many other too, that Elbox (IIRC last year), had implemented some strange protection.

The worst of those strange "protections", could have damaged even the RDB of the HD.

Ciao

[Kent]

If this is coming from the posieden stack, I would email Chris asking for a way to turn off this "feature".  His personal quarrels should not extend further than his own words, putting words in someone elses typing is really pushing it.

:pint:

[Framiga]

Hi Kent

AFAIK, those "driver protection", was implemented on the Spider driver (as Lempkee has made me to remember).

After a strongly protest from a lot of customers, the code has been removed. (or i hope so)

Ciao

PS- except this annoying episode, Elbox remains one of the best and active Amiga related company IMHO
 

[Kent]

Yup I dooly remember that one.  Very hard to forget it.  What I really don't understand is the fight between Chris and Elbox.  How and why did it start?  Is it another one of those "I'm not getting paid per license" type of issues?  If it is, I can't say I would stand behind Chris on it, I've been burned on that issue once.  The best way to get an idea of how many posieden stacks are out there, put it in the program that requires registering the program itself through a web site or mail or email.  Validate the s/n on the card with the list of cards gathered from the parent company (in this case Elbox), for each valid user, request a specified amount from Elbox.  Why would a company want to make an assessment on something they know would cost them money.  What should be done in the first place is to negotiate who will be making the assessment and who will cover those costs.  As a software developer, you should know who your clientel is.  If the parent company purchasing the B2B solution wasn't satisfied with previously mentioned steps, then the contract isn't worth it.  The only other solution is to offer an up front fee with update costs.  Say once a year you will provide software updates to fix potential bugs for a set amount.  That amount could be negotiated each year depending on the requests for software updates.

In the programming industry you have to prepare yourself to be burned, otherwise you will get burned.  Now I'm not sure if this is what actually happened, but from the hilights of the bickering, it looks likely.

:pint:

[Zadoc]

AFAIK, those "driver protection", was implemented on the Spider driver (as Lempkee has made me to remember).

The only report of this 'driver protection' was from Spider users who e-mailed Elbox privately.

Reports claimed that Elbox was going to refuse it's drivers (for Mediator, FastATA, as well as Spider drivers) to function if used in tandem with an E3B product - apparently in retalliation for Chris Hodge's refusal to sell Poseidon registration keys.

Personally, myself, a Mediator owner, I have not recieved any updated drivers containing this 'lockout' - (which for the record if this was planned I was violently against)

I own a Highway card in addition to my Mediator and I would prefer not to be locked out of usage of the Mediator busboard or my Highway card.

While it is possible that this measure was planned, it wasn't to my knowledge implemented (thank god!) as I haven't recieved any modified drivers.

Personally, it seems like the users of Poseidon and Elbox products (and in some cases, owners of E3B products) are the ones getting shafted so to speak.

I'm rather tired of these childish fueds between Chris Hodges and Elbox and feel terrible that Michael Boehmer is also being dragged into this simply by being associated with Mr. Hodges.

PS- except this annoying episode, Elbox remains one of the best and active Amiga related company IMHO

I wholeheartedly agree...just as I agree that Chris Hodges is doing a fantastic job on bringing USB to classic Amigas, Amithlon systems, and MorphOS through Poseidon.

I can't fathom my Amiga without a Mediator or without Poseidon USB stack.

It's a shame that both of their behaviors sour the fruits of their labor.

[Zadoc]

@ Kent:

So it works on the shell without launching any programs? (holding down both mouse buttons)

Sort of...Holding both mouse buttons down and booting without a startup sequence binds the keyboard to the 'bootkeyboard.class'

While bound to the 'bootkeyboard.class' I can type 'Elbox' without the 'bug' respelling it for me.

Afterwards, I added "MUI:Libs" to my Libs: assign, and "MUI:Locale" to Locale, did a "mountenv" and fired up "Trident".

After I bound the "hid.class" to the keyboard, the "Elbox" bug returned.

[Kent]

Yeah, I'd ask Chris how to remove that "feature".  If there is no way to remove that feature, I would ask for a feature request to at least be able to turn it on and off.  For now, don't use a USB keyboard I guess.  Sad how some fights go as far as programming, but oh well.

:pint: