@orgin

Quote:What's wrong there? Hyperion did implement it in U-Boot/PPCBoot, using the SciTech emulator. Without it there would be nothing on the gfx card in U-Boot and you'd have to use a serial terminal for changing U-Boot settings or to select a boot configuration in the SLB.

mine is the best in the world.. eheh

@Swoop

Yeah, I read it. I just want to be sure if I understand it correctly.

Is there any last.fm software for AmigaOS? I know there's a MorphOS AmigaAMP plugin, Amiscrobbler.

@mailman

From the readme:-
Quote:

@MamePPCA1

Have you tryied the Warp3D GPU plugin? For games with not much textures it speeds up FPSE and makes the graphics look much better, but if there are too many textures, all the textures can't be fitted in the Graphic memory and use the standart Amiga memory, which slows the speed considerably and you should use the GPU pete driver for these games.

@MamePPCA1

Quote:
What format are these games? With Hatari I had no problems running all the Atari ST games I found on the net. Once you configure Hatari properly, everything works fine, even with Joystick via AmigaInput. The only problem I can think of which may arise is if you use the included in the archive EmuTOS which is not much compatible, especially with old games. You have to find original Atari TOS ROM - 2.06 works fine, but some of the older games work only with TOS 1.0x.

Quote:
What kind of HD you install? Is it Image file or standart Amiga Drawer on the Amiga File System? The latter is better - you unpack the archives directly in the Amiga drawer and run them from Hatari.

Quote:
All the games I played on the AtariST run fine, and even some of the STE games work nice - like Obsession Pinball. The Falcon Games are still without sound (no DSP emulation yet), but I was able to run some falcon Software as well.

Quote:
I use ROM - TOS 2.06, Screen Options - Use Borders, Zoom ST-low res. Frame skip: OFF (but you can use frame skip 1 for graphic intensive demos (plasmas with scrolls). Sound is at Medium Quality (22kHz), because I see no difference between it and the High (44kHz) quality with the YM emulation. The System is set to CPU type: 68000, Machine type: STE, CPU clock (MHz) - 8, Real time clock emulation and Patch Timer-D set. For Memory setup I have set 4 MB. For Joystick I use Generic USB Joystick and "use real joystick:" set. All the games play with the Joystick fine. For games STonAmiga is not good choise because it doesn't emulate the hardware, and the hardware banging games don't work on it. Only the system friendly software, like word processors and Sim City may be. You can't boot games directly from floppies with the Atari ST emulators (I never tryied and I don't have disk drive on my AmigaOne), but for file based games, you just copy the files from the disk to your harddrive and start them directly from there, or better make an image of the floppy.

@ZeroG

Well, I don't own OS4. I just wanted to know if I understand correct what is the purpose of this tool.

I have a very important message to you.

It's about me selling my ?A1-C and needing to change
account name. Sorry for doing it the PM way but I couldn't
get my e-mail account to send you a mail. I got a error
mail, about not being able to send the message, back all
four tries.


@Amigans staff

Sorry for posting this but I need Rogue to see this. He has
told himself that he can miss PM's so it's better to email him.
Now that this doesn't work I need to contact him somehow.
This seems the best way to me.

Thanks for having oversight this one time.

Just bought some classics in hope they make a new PPC card for OS4 to run on with them.

@TetiSoft

It says that it was implemented by Hyperion, which to at least me means that they wrote the code. But supposedly they didn't so I guess the text needs to be interpretated some other way.

@joerg

Quote:

Yes, it does:
VESA VBE 1.2, VBE 2.0, VBE 3.0
http://www.scitechsoft.com/chiplist/snap_linux_chiplist.html

It also supports a lot of cards that are newer than we currently have drivers for. What happened to SNAP? Is it still due to be part of OS4?

btw, the PPC Linux version is still available from http://www.scitechsoft.com/ftp/snap/linux/beta/
It doesn't seem to be listed on the website any more or updated.

Chris

Since installing the July update I have had intermittent crashes when trying to open 320x240 resolution screens. The result is a black screen with a two-pixel high bar along the top which fades between grey and white repeatedly.

I can reproduce it quite easily by running ASp in full screen mode. I have an ATI Radeon 7000.

Here is the crashlog:

Dump of context at 0xEFE27B70
Trap type: DSI exception
Machine State (raw): 0x0000F030
Machine State (verbose): [ExtInt on] [User] [FPU on] [IAT on] [DAT on]
Instruction pointer: in module Kickstart/rtg.library+0x00053BA4 (0x016CF644)
Crashed process: Apps:Emulators/ASp/ASp (0x6A3DF640)
0: 0000000A 6A336C40 00000000 6B940C81 80B352C1 00000001 016C0F20 00000002
8: 000000FF CCCCCCCD 0000000C 00000009 016D0000 6A336EE0 01E50000 01E50000
16: 00000FFF 80000000 0000000E 00000001 016E14D4 00000001 00000001 000000FF
24: 016A7B34 016CF680 00000100 FFFFFFFF 00000180 80B352C0 6B940D80 00000000
CR: 44004028 XER: 20000000 CTR: 00000001 LR: 016CF6A0
DSISR: 40000000 DAR: 6B940C80

FP0 : FFF8000082028000 40019999A0000000 3FDD1758E0000000 0000000000000000
FP4 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP8 : 0000000000000000 0000000000000000 0000000000000000 40DFFFC000000000
FP12: 40E0000000000000 4330000080000000 0000000000000000 0000000000000000
FP16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP24: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FP28: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
FPSCR: 82028000
DSI verbose error description: Access not found in hash or BAT (page fault)
Access was a load operation

Registers pointing to code:
r6 : native kernel module Kickstart/rtg.library+0x00045480
r12: native kernel module Kickstart/rtg.library+0x00054560
r20: native kernel module Kickstart/ATIRadeon.chip+0x00005F74
r24: native kernel module Kickstart/rtg.library+0x0002C094
r25: native kernel module Kickstart/rtg.library+0x00053BE0
ip : native kernel module Kickstart/rtg.library+0x00053BA4
lr : native kernel module Kickstart/rtg.library+0x00053C00
ctr: unknown (0x00000001)

Stack Backtrace:
native kernel module Kickstart/rtg.library+0x00053BA4
native kernel module Kickstart/rtg.library+0x00053BA4
native kernel module Kickstart/rtg.library+0x00045480
native kernel module Kickstart/rtg.library+0x000354D4
native kernel module Kickstart/rtg.library+0x0002B850
native kernel module Kickstart/rtg.library+0x0002C168
native kernel module Kickstart/rtg.library+0x00030D08
native kernel module Kickstart/rtg.library+0x000012A8
native kernel module Kickstart/graphics.library.kmod+0x00021634
native kernel module Kickstart/graphics.library.kmod+0x00004428
native kernel module Kickstart/kernel+0x0004F034
module Apps:Emulators/ASp/ASp at 0x6A35C1DE (section 0 @ 0x41D6)

Disassembly of crash site:
016CF634: 54A507BE rlwinm r5,r5,0,30,31
016CF638: 2C850000 cmpwi cr1,r5,0
016CF63C: 41A6FF48 beq- cr1,0x16CF584
016CF640: 7CA903A6 mtctr r5
>016CF644: 8CA3FFFF lbzu r5,-1(r3)
016CF648: 9CA4FFFF stbu r5,-1(r4)
016CF64C: 4200FFF8 bdnz+ 0x16CF644
016CF650: 38210010 addi r1,r1,16
016CF654: 4E800020 blr
016CF658: A563FFFE lhzu r11,-2(r3)
Stack pointer (0x6A336C40) is inside bounds
Redzone is OK (4)

68k register dump
DATA: 6A17E7B0 80000010 00000040 00009E80 37DFFA6C 00082883 0023003C FFD70001
ADDR: 6A17E7DC 6FF28750 6A18CE40 6A17DCCC 6A30B0C4 01E42194 6FFB4420 6A336FDC
----> 6FF28750 - "Apps:Emulators/ASp/ASp" Hunk 0003 Offset 00000748 (SegList: 0x1A8D6001)
----> 01E42194 - "Kickstart/dos.library.kmod" Hunk 0001 Offset 00000790

@orgin

Quote:
Whats wrong with that? U-Boot can use (nearly) any gfx
board AFAIK, it is e.g. able to create DVI output on
a Radeon and I remember that somebody did send me a
gfx board where OS4 had no driver, U-Boot could happily
use it and OS4 was even clever enough to display the
"No P96 driver for this board" message on the gfx board
(in text mode as initialized by U-Boot) before giving up.

@joerg

I disagree, I think that OS4 could use a VESA driver. As I said, it's not for performance, it's for at least getting a display out of any card you might find out there. Specific drivers isn't growing like weed in mums garden and old cards are going to get harder to find.

If my gfx card broke down I would have to special order a new one from something like ebay or over priced from some amiga outlet. I'd rather be able to at least get it going again using a cheap card from a local dealer than waiting for the postal service to stumble over itself.

@joerg

Something is wrong in the news item then:

Features of PPCBoot (as implemented by Hyperion):

* x86 BIOS emulator capable of initialising and using nearly all PCI and AGP graphic cards based on the chipsets of ATI, nVidia, 3DFX, S3, 3Dlabs (Permedia), Trident etc.


But anyway, that's too bad then. Probably not so easy to reuse it from within os4 then.

@Hans

Quote:Probably because it's wrong The BIOS and x86 emulator in U-Boot is from SciTech (they used it for SNAP), Hyperion licensed it and IIRC ported it to U-Boot as well, but they didn't write it.

@orgin

Quote:U-Boot could set up a VESA gfx mode, but all you'd have is a single frame buffer in a fixed mode, you couldn't switch to different modes in OS4, and using more than one screen wouldn't be possible without ugly hacks like the HAM emulation of OS4 either. To be able to use more than one screen, all in the same, fixed resolution set up by U-Boot of course, for example all screen and other bitmaps would have to created in mainboard RAM and the contents of the current screen would have to be copied for example 50 times per second to the frame buffer, a dumb frame buffer for a single screen would be very slow already, but something like that would be completely unusable.
When AmigaOS4 is started U-Boot is gone, it initializes the system and passes some arguments to AmigaOS4, but it doesn't survive.

Quote:IMHO a VESA gfx driver doesn't make sense, we need a new, faster gfx system using hardware 3D, not something which is much slower than the supported gfx cards. A VESA driver can be used for booting a system which doesn't have a driver for the currently installed gfx card yet to install the new gfx card driver, but not for normal usage.

@Atheist
The lines with @ are just some global settings for your program and you only need a few or even just one in your program. The rest looks a lot like AMOS. I was once an AMOS programmer and Hollywood reminded me a lot of it when I first tried it.

You might want to visit
http://www.amiga-resistance.info/home ... wood/quellc/quelltxt.html
for some example source codes. The page is in German, but you can still try the download links.

Alex.

@orgin

Quote:

I thought so but couldn't confirm it. If they wrote it, they should be allowed to release it under a dual license (i.e., a GPL version for UBoot and proprietary version for the driver).

Actually, I'd prefer it if they concentrated on a new graphics API/driver system that will rid us of the limitations of the current one that are ruining 3D performance. As I said earlier, a Radeon x1### PCI card could be used to develop the new system on the same machine that's using the old system for the AGP card. That way you'd still have a working display on the machine while developing and testing the new system. If you're really stretched for cash, you could use a KVM (for it's monitor switching only) so that you don't need two monitors.

Hans