Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Amiga Software News => Topic started by: bloodline on February 28, 2003, 08:34:38 PM
-
Yet another version of AROS is avaiable for your pleasure.
This is the first version where I recomend the CD-ROM over the Floppy disk version.
Please note, new graphics driver allows Hi-Colour (16bit) and True-Colour (32bit) screens.
There are still a few bugs, so please read the readme or the news page on my site.
http://www.ahsodit.com/aros/
-
I'll try it tommorow. Anybody knows how the native
compiler progresses ? /me is waiting for C++ :-D
@moderators
Completly wrong category ;-)
-
Aros is getting better and better each day.
-
yeah, and no problem with hardware to run it on ;-)
Dan Andersson
-
The native c++ compiler is coming along... slowly :-P
No doubt Fabio will post something here later to give you a better idea of the progress of that.
Also, I recomend you use 640*480*16 on the graphics mode at the moment they work the best at the moment. :-D
-
Article updated. Category changed along with the link updated and verified.
Oi, it's just been one of those days...
:pint:
-
I'm not sure emulation is the right category either... actually I don't know if there is a category for AROS... :-D
-
What the heck is AROS doing under "Emulator" when it's not an emulator? It's an API compatable AmigaOS clone. It can't even run AmigaOS binaries (unless you're on an Amiga). It clones the API, provides new options, but is not an emulator under any definition of such.
-
I was about to ask why this new is under the "emulation" category too!
AROS is not an emmulator! Don't make it look like one...
:-?
-
Anybody knows how the native
compiler progresses ?
It's coming along, as Matt already said. There's quite some way to go yet, though, since I want to do a clean job.
Right now the binutils (that is, the linker, the assembler and a few other tools) are being worked on and almost finished in their cross-platform version, meaning that you'll soon be able to download the latest version of the binutils from the official source and you'll be able to configure it to produce code runnable under AROS.
Right after the binutils I'll tackle gcc, which will be a much easier job. Still in the "cross" form, though.
Then, with those tools, I'll be able to attempt a native compilation of the binutils, and then of gcc. But for this to happen in a clean way some work will have to be done on the AROS' libc, since right now it's missing most of the signaling stuff.
All this is done in my spare time, which I'm not rich of these last days...
-
didn;t run on my machine :-( VGA just resets the machine, and the rest come up with funny gpahics at the top of the screen
-
didn;t run on my machine VGA just resets the machine, and the rest come up with funny gpahics at the top of the screen
Typical... there's always one isn't there!!!! :roll:
What Gfx Card and CPU do you have?
-
didn;t run on my machine VGA just resets the machine, and the rest come up with funny gpahics at the top of the screen
You should record a list of the hardware on your system and forward it to the AROS team. The most important will be cpu (not likely to be a problem), motherboard chipset, graphics card (most likely) and other cards.
The standard VGA works for me but none of the other modes (garbage at the top of the screen). Lucky me and my Savage 2000 based card... #$%@* S3 and Diamond!!!
-
Well, I've had no problems with 640*480*16 on:
Several models of; Nvidia, ATI, Matrox and a Trident Blade3D (Almost forgot the integrated intel gfx that one machine had).
I've not tried a Savage card, as I don't have one.
-
actually I don't know if there is a category for AROS...
Yeah, an Aros category would be very cool, Aros isn`t an Emulatror.
I `m downloading the cd version now ;-)
I`ll have the new AmigaOS in my new Amiga, and Aros in my PC when it will be more complete :-)
-
bloodline said:
I've not tried a Savage card, as I don't have one.
I tried it on an ATI Radeon 7000 and an 8500. It produced what looked like a number of miniature versions of the display in a row across the top of the screen in all modes but VGA. My Linux box has a Trident Savage4. On that hardware, the non-VGA modes caused it to output the display at 15.8KHz. Of course, my monitor can't display that. :-(
However, the VGA mode worked on all my machines.
-
Typical... there's always one isn't there!!!! :roll:
I am sorry that I have the only configuration, out of the almost invinate conbinations, that breaks your program.
If that is your attitude then I will think twice before I waste another CD on the AROS project.
For the record I have a:
1.4GHz Athlon Tunderbird
iWill KK266plus motherboard
(if i can ever get to iWill's website i'll say which chipset)
Radeon 7500 (powered by ati)
768Mb RAM
SouundBlaster 5.1Live!
Generic PCI LAN card
Kayboard
USB mouse
-
@falemagn
Actually the crosscompiler is even prefered here ....
It is just that sometimes ago someone told me that C++ would
only work once the native-gcc is done.
-
If that is your attitude then I will think twice before I waste another CD on the AROS project.
Ehy, dude, calm down! Matt wasn't attacking you at all, he was just being ironic :)
-
It is just that sometimes ago someone told me that C++ would only work once the native-gcc is done.
No, don't worry, that's not the case.
Actually, you could use C++ right now already, however you won't be able to use the standard C++ library nor exceptions, since those things need to be specifically adapted to AROS.
-
The AROS-team are really doing an amazing job!
...and that without getting payed......
a big hug and kiss to you all!
-
Problems with 16/32 bit modes on AthlonXP/Radeon7500 here:
either I am only getting some trashed line at the top
of the screen... either simply black screen...
VGA works fine.
Regards,
Leo.
-
Mmmh you mean classes with virtual-fucntions and so on now work ?
Cool :-D
-
If that is your attitude then I will think twice before I waste another CD on the AROS project.
Oops sorry Jumpship... I didn't mean to offend, that's why I put a smilie at the end of the sentence. I was just being Ironic, since I imagine that that quite a few machines won't work. I have tried to test as many different configurations as I can. I will always list any compatibility problems I find.
As soon as you listed your machine specs, I was on to my friends to see if any of them had a similar configuration to yours, so I could test it.
Sadly all my friends are really cheap and 90% of them have Geforce2 mx's...
It seems that there is a general trend of Radeons not working, If you (and several others) hadn't posted that information, then there is no other way we could have found that out!!
So I thank all of you who have provided feed back as to this latest release.
-
I will think twice before I waste another CD on the AROS project.
Guys you should use a rewritable CD. You can`t burn cds every time they release a new version.
It would be very nice if there was a list of the supported hardware.
-
Mmmh you mean classes with virtual-fucntions and so on now work ?
Yes, they do. However. you'll have to define your own operator new and the like.
-
I would love to have a list of supported hardware, but until I get back the bug reports from you guys, I have to assume it will work on all Pentium class machines with VESA2 compatible Graphics cards(as it should!).
By the way, I like your Epicurus Avitar, Epicurus being my favourite philosopher.
-
This reminds me, I need to finish up that tulip driver for AROS that I promiced I'd work on.
-
Very impressive Matt........nice music too!
Bob C.
-
@bloodline
Sorry, I didn't mean to have a go at you, I guess I wasn't feeling very ironic this morning and misread the smiley you used :-)
Hope that the info helps out.
Once again sorry for "jumping" (no pun intended :lol:) off the deep end at you!
Jumpship
-
Hallo there again :)
It worked fine on my room-mate`s Athlon 1700+ xp 512Mb DDR with TNT Riva. I tested both the the last choice (was it 1024x760?) and that 800x600x16. The bug with the ponter didn`t occured.
Unfortunately I couldn`t test in on my PC with nVidia because my DVD couldn`t read my RW-CDs :-/
Will the pull down menus (AmigaOS style) be implemented on AROS?
-
Will the pull down menus (AmigaOS style) be implemented on AROS?
The menus can be configured anyway you want!
Send me an E-Mail and I build you one with AmigaOS 3.1 menus (ie no magic menu style menu)
-
Very impressive Matt........nice music too!
Thank you!! pretty good examples of how useful the Amiga still is for music!! Which also hints at my main interest in AROS ;-)
Since we signed to Ahsodit we have been working on another 6 songs... we will see how it goes.
-
Worked fine here. Nice work guys.
-
I've not tried a Savage card, as I don't have one.
The card is a Diamond Viper II which is very different from the conventional Savage cards. Totally different chip using a similar name. Sadly it got abandoned when Diamond went Sonic Blue and S3 went to VIA.
In 16 bit mode there appear to be four images of what's supposed to be the screen across the top of the monitor.
In 32 bit mode it's similar but much smaller and more images across.
Neither is readable but you can see pixels change when you move the mouse pointer around.
-
Booted just fine on my laptop except:
The mouse is stuck in top/left corner and won't move.
My system is:
Toshiba 5106-S607 Laptop
P-4M 1.7 ghz
GForce 4 440 Go (32 meg)
512 memory
40 gig HD
Mouse: Logitech TrackMan Wheel USB
Keyboard: Microsoft Internet Pro USB
Note: Can't use non-USB mouse/keyboard (no ports).
Keyboard worked fine and I could use the shell with no problems.
Have only tested VGA mode so far.
I will test on my other desktop systems in the coming days.
Loki :-D
-
O.k. now I tried it:
No chance on the Laptop (Ati-Rage), but one of the pre-wanderer
images did work.
Only VGA on the AthlonXP (Matrox-G550).
I think I'll stick to the hosted version for a while.
-
In 16 bit mode there appear to be four images of what's supposed to be the screen across the top of the monitor.
In 32 bit mode it's similar but much smaller and more images across.
Neither is readable but you can see pixels change when you move the mouse pointer around.
Hmm ... sounds a bit like a bytes-per-line problem.
Are the colors on screen (ignoring gfx garbage)
ok. Ie. do you see white/black/amiga blue/amiga grey?
I could send you some modified floppy images,
to possibly find out what the problem is. If you
want send me an email: georg.steger@rolmail.net
-
Hmm ... sounds a bit like a bytes-per-line problem.
Are the colors on screen (ignoring gfx garbage)
ok. Ie. do you see white/black/amiga blue/amiga grey?
Nope... colors are wrong as well. (from memory) It's mostly a black background with some lines that are obviously the Worbench title bar and the outlines of any windows. The strange part is that the outlines change color when you pass the mouse pointer (a few pixels) over them.
I'll drop you an email and serve as tester for a while.
-
I have tested it on my office computer now with the following results:
1. Appears to boot in all video modes.
2. All video modes appear the same (no difference in the sizes or colors of any objects).
3. Could not get any programs that open screens to run: said "requires 16 bit or true color to run" or just said "Could not open screen".
4. Mouse works good on this machine: Logitech TrackMan Marble (PS/2 type).
This system:
P4 2.0 ghz
ASUS P4B533 MB (Intel 82845E MCH, 82801 DB ICH4)
512 M DDR memory
GForce 4 Ti 4200 w/128 M memory
30 gig Maxtor HD
20 gig Maxtor HD
48X Creative CDRom
40x12x48x JustLink CD-RW
NetGear 100/10T PCI
Loki :-P
-
Well, after some emails back and forth... my Diamond Viper II is now working in all modes I've tested.
The fix should solve the problem for people that saw something like I described above.