@hardwired

At the moment it compiles for OS4, MOS and OS3. While AROS is another possible target, there are currently no plans for it. AFAIK nobody of the team uses AROS, so all depends on time, motivation and needed effort for such a port.


But as said, the current OS4 beta is meant to collect more user feedback. In the near future, OS4 will probably stay the only release target for beta versions. Eventually there should be an automated nightly build system and the situation should change.. Until then, please be patient :)

_________________
Regards, Cyborg.
AmigaOS4 development team member

"In the beginning was CAOS.."
-- Andy Finkel, 1988 (ViewPort article, Oct. 1993)

Very cool news! i love Amirc. but i will continue to use wookiechat as long as amirc doesn't support utf8. Too many people are using it in the swedish channels i'm visiting so it makes it hard to read the swedish characters.

Cool to se that AmIRC still is alive...using it 8-9 years every day..But when I go to OS4.1 using Wookie chat is nativ and very easy to use.... But now again I will test AmIRC ;)

_________________
--

Amiga x5000 ı o2o ı 4GB RAM ı RadeonRX580 | SBlaster Audigy Fx - AmigaOS4.1 FInal Edition

A1200 sandwich :)

Croatian Amiga portal

@smf

You should check the releasenotes ;) It supports charset conversion through codesets.library now. (which is one of the things which need extensive testing)

_________________
Regards, Cyborg.
AmigaOS4 development team member

"In the beginning was CAOS.."
-- Andy Finkel, 1988 (ViewPort article, Oct. 1993)

@hardwired

I still prefer using it over mIRC for example. Actually over any IRC client that I've ever tried and I tried a bunch in Linux. There is something about the design that is very simple yet powerfull. Easy to use and powerfull, I haven't found that combination anywhere else. I actually think it looks nice too and has always worked really well and stable. I've used WookieChat for a long time now but I'm back to AmIRC it seems . Both are really nice though.

@samo79

Thanks. Looks like my previous install of AmIRC V3.5 had timed out due to lack of registration. I installed it quite a while ago to see how it worked on OS4 (it worked fine at that time). Reinstalled AmIRC V3.5 and dragged the new files into the drawer and working ok now.

Thanks to all involved.
redfox

Last edited by redfox on 04-Jul-2011 at 04:03 PM.

@samo79
I thought it was discontinued years ago, so this thread came as a nice surprise.

@Cyborg

I see. On the other hand problem with AmigaOS strings is that it feels odd on AROS or MorphOS... But then I have always used my custom Finnish catalog which is much better than the official one :-p

It is good idea concentrate beta testing only on one platform. Of course I would have wanted new AmIRC using new MorphOS APIs but you can not always get everything

Knowing Vapor products it must have been very pleasant porting effort

Last edited by itix on 04-Jul-2011 at 04:44 PM.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

@Andre4s

ScreenShot : http://amiga-ng.org/resources/Amirc3.12.jpg

_________________
PowerMac G5 2,7Ghz - 2GB - Radeon 9650 - MorphOS 3.14
AmigaONE X1000, 2GB, Sapphire Radeon HD 7700
FPGA Replay + DB 68060 at 85Mhz

@K-L

One more :)

_________________
Join us to improve dopus5!
zerohero's mirror of os4/os3 crosscompiler suites

@itix

Quote:

itix wrote: I see. On the other hand problem with AmigaOS strings is that it feels odd on AROS or MorphOS... But then I have always used my custom Finnish catalog which is much better than the official one :-p

Don't worry, I think this should be easily solvable :) It just wasn't that important back when I changed all the strings.. in fact, at that time, I didn't even think about other systems than OS4, simply because I don't know anything about them or because I would have to clutter the code with #ifdef's .. well, eventually the #ifdef's were introduced/kept and compatibility too...

When I have the time I'll see if I manage to setup everything needed to compile MOS and OS3 versions... but please don't hold your breath for that.

Quote:

It is good idea concentrate beta testing only on one platform. Of course I would have wanted new AmIRC using new MorphOS APIs but you can not always get everything

A wise man once said: "First get the thing stable, then make it fast" .. replace "fast" with "use new APIs" and you know what I mean

Of course, being the OS4 dev that I am, I couldn't resist implementing some new OS4 features like the notification or URLOpen system

Quote:

Knowing Vapor products it must have been very pleasant porting effort

Ehem.. well.. the source was/is... "interesting"... in many respects There was a reason why we had a hard time to get it even to compile with GCC

_________________
Regards, Cyborg.
AmigaOS4 development team member

"In the beginning was CAOS.."
-- Andy Finkel, 1988 (ViewPort article, Oct. 1993)

@Cyborg

WOW, thank you for resurrecting this!!
Also great to see it taking advantage of new OS features like Ringhio notifications

_________________
Proud Amigan since 1987
Owner of various Commodore and a SAM440ep\OS4.1FE
See them on http://retro.furinkan.org/

@Tomas

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

Nice to see its coming for most amigasystems. Took me some while to go from AmIRC to wookiechat. I have so much stuff Jahc put into gui that i like so AmIRC will be there too for testing purpose.

Good work Team :)

Last edited by Kicko on 04-Jul-2011 at 06:56 PM.

@Cyborg

Quote:

Ehem.. well.. the source was/is... "interesting"... in many respects

Vapor developers were one of the best Amiga developers I have ever met

Quote:

There was a reason why we had a hard time to get it even to compile with GCC

Humm? The latest source code committed was already ported to GCC? SAS/C dependencies were resolved long ago and committed.

Last edited by itix on 04-Jul-2011 at 07:17 PM.
Last edited by itix on 04-Jul-2011 at 07:16 PM.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

@itix

Hmm... good or not their browser Voyager I never liked. The last versions was *really* slow when it comes to scrolling on my a4k and it's the only browser with that behaviour that I know of. With NG machines it isn't as obvious though. On my old a4k it was fast with IBrowse, AWeb, Netscape, iCab (runing under Fusion/Shapeshifter).

Also it always fealt like work in progress compared to IBrowse and AWeb. The other programs where more or less good though and AmIRC I used a lot.

EDIT: Sorry for going OT

Last edited by hotrod on 04-Jul-2011 at 10:48 PM.

@hotrod

I never liked Voyager much. In my opinion IBrowse UI layout and gfx style was always better than in Voyager. But as developers they were great -- there apparently was (as I dont know Vapor personally) technology sharing between different Vapor products developing some interesting methods for Amiga coding.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook

@Cyborg

Quote:

@smf You should check the releasenotes ;) It supports charset conversion through codesets.library now. (which is one of the things which need extensive testing)

I did read it but apparently i was blind.. but now i can see it :p this is great

@itix

Of course Oli and Jamie did an excellent job with AmIRC and all their other tools.. but the source (at least of AmIRC) is in many respects strange and in parts very dangerous, because based on assumptions about OS-internals or because of the use of MUI internals, which are private for a reason.
OTOH coding style changes over time and most of the time, the coding style says very little about the capabilities of a developer

Yes, the code (3.5.28 baseline) was already prepared for GCC, otherwise, it wouldn't have been compilable for MOS, right?

My sentence was a bit misleading.. indeed we had problems getting it to compile properly with GCC 4.x. But most work went into fixing DSI (OS4 doesn't forgive that much than OS3/MOS), re-implementing missing functions (especially from VAT), making it compilable for all three OS3/OS4/MOS, etc.

But actually the first somewhat working compile after fixing the most pressing issues was done with SAS/C

_________________
Regards, Cyborg.
AmigaOS4 development team member

"In the beginning was CAOS.."
-- Andy Finkel, 1988 (ViewPort article, Oct. 1993)

@Cyborg

Back then Vapor developers were contributing to MUI and knew each others well, knowing which methods and attributes are safe and marked public in future releases etc. But it is indeed dangerous. Voyager and HTMLview.mcc (and IBrowse, too, but was worked around) stopped working in MUI 4. I would not be surprised to find specific AmIRC workaround in MUI source code.

Not sure about Enforcer hits. I am sure Nicolas Salling fixed them all if there were any.

Edit: DSI hits could be side effect of ELF file format because 68k excutable format does not define read-only hunks. Strings were always writable.

Edit 2: oh I see, you didnt have source code to vapor_toolkit.library ...

Last edited by itix on 07-Jul-2011 at 08:55 PM.
Last edited by itix on 05-Jul-2011 at 10:17 AM.

_________________
Amiga Developer
Amiga 500, Efika, Mac Mini and PowerBook