Hi

I’ve installed Parmesan on SARPC & Kinetic (RO 4.37 & 4.39) and My Iyonix, where it works fine.(It’s the nicest fastest MSN client I’ve used.)

I’ve also installed it on a Mico (RO 4). On the mico it runs but reports lots of errors (at seemingly random times):

11:43:27.48 * WimpError * from Parmesan Error : &6C66664F Message: Unexpected error from MSN server (code %0)
11:44:09.28 * WimpError * from Parmesan Error : &6C66664F Message: Unexpected error from MSN server (code %0)
11:52:51.85 * WimpError * from Parmesan Error : &6C66664F Message: Unexpected error from MSN server (code %0)
12:04:04.03 * WimpError * from Parmesan Error : &756D6153 Message: Unexpected error from MSN server (code %0)
12:05:06.74 * WimpError * from Parmesan Error : &34303432 Message: Unexpected error from MSN server (code %0)

It recieves files, but cannot send, usually giving one of these errors.

I think think a problem with the mico may be the cause.

cheers

I think these problems are related – sending your display picture to other clients uses essentially the same mechanism as sending files, so the seemingly random times you get these errors will be whenever another client asks for your picture.

As to what’s causing it, I’m less certain – I’ve had a bit of a think about it and probably the most likely cause is the C library on the Mico. Parmesan uses certain features only present in Castle’s (32 bit) C library, so please make sure you’ve got this installed (there’s a link to download it on Parmesan’s own download page), and see if that helps.

Yes, I can confirm that the Mico doesn’t appear to send display pictures.

I have installed the Castle C library, but that makes no difference.
(Probably already had it.)

I have tried Parmesan on an A7000+ (3.7) and it works fine.

Would it be possible to make non fatal error messages less intrusive?
(eg appear at the bottom of the main contact window.)

Also I notice that display pictures can look horrid in 256 colours, is it possible to tweak the tict settings to fix this, or ultimately let the user change them?

I’m afraid I’m going to need some help to track this down – if you send me an email (address on the contact page of the website) I’ll give you a copy with some extra debugging code in it. If you don’t mind running this and provoking the problem that would help enormously.

Sorry about the intrusive error messages, that was one of the things I meant to improve for this release. They’ll be quieter in the next.

As for Tinct – yes, it looks like I can improve that too.

Thanks

I now no longer think this is directly a problem with Parmesan, I think it is the Mico networking corrupting data. (I have now seen problems with other network programs).

The Mico is no longer installed (it was set up at my parents’ shop, but I have put my Risc PC there instead.)

If you feel it would be of any help (to the program as a whole) I could test it, but since it doesn’t kill the program, if I’m right about the Mico, it won’t be of any help.

That’s interesting, thanks. The current release of Parmesan should at least tell you what error occurred (there’ll be a number where it used to say %0) – otherwise its error reporting should be a bit quieter. It’s slightly odd that it affects file sending only – it does sound like my fault rather than a general networking issue. Has anyone sent files successfully on a Mico?

I’ll try to get it hooked up again some time, however it may be worth pointing out the trying to use the networking on Select didn’t work (stiffs the machine IIRC).

I also wonder if there are (m)any other Micos on broadband.