Hi devs (and those who want to be),

the new version of Evilrich's SDL port works fine so far
(i just build a project with it), but it has two minor
flaws which need to be addressed.

sdl-config has a wrong prefix set (both in clib2 and
newlib), in the downloadable archives it's set in
local/newlib/bin/sdl-config to
prefix=/usr/local/amiga/ppc-amigaos/SDK/local/newlib/
respectively in
local/clib2/bin/sdl-config to
prefix=/usr/local/amiga/ppc-amigaos/SDK/local/clib2

Both of these won't work and will throw errors on not
finding SDL.h. they need to be fixed to point to the right
drawer, for newlib it has to be
prefix=/SDK/local/newlib
and for clib2
prefix=/SDK/local/clib2

Of course you dev and porting gods do know about it already
and know how to fix it, but me (and probably lots of other
poor sods who pretend to develope/port for our
beloved system ) didn't know and might find this
information useful.

/me signing off

now get to work and port beautiful stuff with enhanced SDL

@spotty

Wouldn't this make an addition to your pfd?

@agafaster

IPF(ilter)

...but i think it's rather difficult to get working, get a
router with firewall.

@Jack

Hmm, i know this behaviour from my HD's (plugged in through
an USB to IDE connector). As soon as they are formatted
under WinXP (NTFS, i think) they can't be seen. I HAVE to
format them with FAT32 at least.

@Jack

I tried something similar.

Just for the fun of it i wanted to do a complete build of
ScummVM on my ! GB stick, complete with checkout, linking,
building and running the exe from the stick.

I didn't even got the source code

6.PConKey:> svn co https://scummvm.svn.sourceforge.net/svnroot/scummvm scummvm
svn: REPORT request failed on '/svnroot/scummvm/!svn/vcc/default'
svn: REPORT of '/svnroot/scummvm/!svn/vcc/default': 400 Bad Request (https://scummvm.svn.sourceforge.net)

is everything i get to see, although this is a perfectly
valid command and works otherwise both on my HDs and in RAM:

I have CrossDOSFS installed, but i think i formatted it
inbetween, so i assume it's FAT32 i have on it.

Problem is i need the FAT fs to stay exchangable betweem
platforms.

I hope these glitches can be addressed someday

@MichaelMerkel

Quote:
No, otherwise it would be a little funny posting this, wouldn't it?

May i hijack this thread

Maybe i find someone who has (or had) similar problems

Anyone got a "broken" checkmark button (cut in half from
the little picture next to it) when first opening the AU
window after an update is found?

It's no biggie and it certainly don't degrade AU in any way
(well, in a small way for me) but it's annyoing (at least
becasue i can't find out WHY its happening)

I got back to default GUI (no bells and whistles) and it
changed nothing

Any ideas, thoughts, help?

Thanks a lot and sorry for hijacking

@Snuffy

I don't have this JukeBox thingie installed, my Push4Dock is
completely custom (well, apart from some programs everyone
needs, that is)

I also don't get Grims with TN, never, it's stable as rock,
just this annoying docky problem, maybe i'll have to write
to Mason, too?

@PEB

Nope, didn't try that until now and it didn't cure my problem

but thanks for the idea

@Raziel

soooo?

anyone got the same problem or not at all?

someone has a workaround maybe?

@Mikey_C

I gave it a shot one or two times in the past, but got stuck
everytime in the linking process, ti does something nasty i
sadly can't figure out...some more experienced builder has
to step in here and get it sorted (and probably let it go
into SVN too, so other non-experienced builders can build
it afterwards too)

Since some weeks, i get this specific error message from TN
whenever i try to open it (no matter if through a script,
AWeb based call, rexx based call, drag&drop, etc.)

I'm using Push4Dock in it's latest version

Any ideas whats wrong?

@Rigo

I just sent a log to a similar error (i think).

It seems AU can't find a file and breaks/crashes
I am not able to updtae to 1.87, even if i cancel the auto
update and do it later by scanning, it just breaks with
the message "Can't find file ''" everytime.

@Amigamancer

Quote:
You don't need eUAE to run classic program/games on a classic
system, just put in the disk and run them.
(if you have a high end system and programs refuse to run, it's
not AmigaOS3.x fault either to not support them anymore, isn't it?
If you want to play games - EVERY game - try out WHDLoad)

Furthermore, as often stated, AmigaOS4 is NOT developed to
act as an exchange to (e)UAE and/or any other "amiga emulator"
out there, it's a NEW OS, featuring NEW components.

It's getting boring to hear reasons why old/classic software
must be supported by AmigaOS4 ... use your classic for them
and enjoy the NEW AmigaOS4 with all the NEW stuff coming for it.

I, for one, am glad that every backward compatibility to
READ hardware banging stuff READ wasn't even considered
anymore at a certain point of development.
Why fix the errors of others?

Looking forward to new awesome features of furutre AmigaOS4.x

@klesterjr

Ooooohhh

Theres an artist one the loose, quick, somebody, grab a paintbrush

@Jack

Dr. Seuss, eh?
The guy with that hatted cat and "The Grinch"?

Not mine, though, have fun

If a packet hits a pocket on a socket on a port,
and the bus is interrupted as a very last resort,
and the address of the memory makes your floppy disk abort,
then the socket packet pocket has an error to report!

If your cursor finds a menu item followed by a dash,
and the double-clicking icon puts your window(s) in the trash,
and your data is corrupted 'cause the index doesn't hash,
then your situation's hopeless, and your system's gonna crash!

If the label on the cable on the table at your house,
says the network is connected to the button on your mouse,
but your packets want to tunnel on another protocol,
that's repeatedly rejected by the printer down the hall,

And your screen is all distorted by the side effects of gauss
so your icons in the window are as wavy as a souse,
then you may as well reboot and go out with a bang,
'Cause as sure as I'm a poet, the sucker's gonna hang!

When the copy of your floppy's getting sloppy on the disk,
and the microcode instructions cause unnecessary risc,
then you have to flash your memory and you'll want to RAM your ROM.
Quickly turn off the computer and be sure to tell your mom!

Happy New Year everyone!

@spotUP

Quote:
Arrghh, stupid 2007, go away already...

@tboeckel

Understood...

/me goes back to his hiding place

@MamePPCA1

Hmm, only two things you could try (which i see from your
config)

Quote:

Change those to (one after another with trying on each change)

TCP/IP - settings
FIRST UserName under Send Mail (SMTP)
User name: javitull

and

Receive Mail (POP3)
Account name: javitull@pop3.telefonica.net

and see if THAT makes a difference

@Atheist

OT:

Quote:
I, for one, slipped out of crunching with my AOne completely,
i no longer want to have the "Fear of Frying"(tm)

Anyway, since the RC5 effort was more or less "cancelled",
many ex-RC5'ers got back to OGR.
Before we didnt stand a chance and now we don't stand a
chance either - it's about showing the underdog has a sharp
teeth? Well, i think we did already - and will be in future
too, but not with showing off our systems...

And, the most important part is ...
one of distributed.net ads says:

Put your cpu cycles to good use!

Well, i do, i run Amiga OS4 with it