@Atheist Quote:
You do NOT need to know C to use PortablE! PortablE generates the C code for you, you give that to GCC, and then GCC gives you an executable.

With the latest (r3) release of PortablE, there is even a script (PE-GCC) which will call PortablE & GCC for you, so you do not even have that to worry about

Quote:

Quote:
Have you tried Jason Hulance's Beginners Guide to AmigaE? (Both ECX & PortablE are based on AmigaE, so you need to understand that first.)

Really, AmigaE is about as friendly as you can hope from a compiled language. Otherwise you will be stuck with much slower interpreted languages like Hollywood (which I think you should try), AMOS, etc.


P.S. I'm not sure what you mean by "Programing Languages for ... the Average Person". I started by learning BASIC on ZX Spectrum & ZX81, then Amiga Basic on an A500, then AMOS on my A1200, before deciding to use a real programming language & learning AmigaE. If *you* are able to learn one programming language, then you can learn another one. If you *can't* then IMHO I think it is you not being prepared to learn a language that doesn't look like AMOS.

@tonyw Quote:
That is actually incorrect, a lot of Amiga games were written in BlitzBasic, a few of them even commercial. e.g. (Super) SkidMarks, and Zombie something-or-other. I think the first Worms (or at least it's prototype) was done in AMOS?

@Slayer
No, I followed Mikey_C's Idiots Guide. edit: It does not seem to contain anything helpful

I'm desperately trying to get decent file sharing between my Sam440 (OS4.1) and my Windows XP Pro SP3 box, before I can seriously use OS4.1, and things are not going very well:

Writing files from the Amiga to Windows box using SMBFS is incredibly slow (reading is fine), so I am trying Samba v2.2.5 instead. My Windows box can *read* files fine from the Amiga using Samba, however...

Windows is unable to *write* files to the Amiga, if they are 4096 bytes or larger! In those cases Windows reports "The request could not be performed because an I/O device error. (1117)". Checking the Samba logs, I see something like this:

Quote:

I have tried fiddling with all the smb.conf settings I could find (especially using the 'secret' web interface that runs on port 901 of the Amiga), but nothing seems to make any difference. I have also tried different filing systems (SFS/00, SFS/02 & FFS) without luck. Can anyone suggest anything?

@joerg Quote:
One bad block does not mean the HD will die, but it does mean it's possible. Certainly doing a back-up before trying my fix would be a good idea, but everyone should keep a backup anyway...

@kvasir
Hard drives automatically handle bad blocks, but AFAIK they only "fix" the bad block when you attempt to write to it (i.e. reading doesn't do anything).

Therefore copying all the files onto itself (overwriting all the files) should fix it. I guess that copying everything into another partition (or a sub-folder) and then back again would work as well.

@Mikey_C
J?rg Strohmayer for OWB, and Chris Young for Netsurf.

I used Fat95 on Amithlon only a few years ago to access various Windows partitions (including large files), and it was rock-solid in my experience.

But IMHO the CrossDos problems with USB sticks on Sam440 is more likely down to the crappy USB support in the beta version of OS4.1...

@tlm Quote:
Does this mean that your Sam440 came with an offical I/O backplate?

@acefnq
Some good news from m3x (ACube employee) on AmigaWorld, is that they have fulfilled 75% of their Sam440 back orders. So presumably not too much longer wait for you...

BTW, regarding DVD playback problems with DvPlayer on Sam440, it is only for non-Region-0 discs, and is simply due to a DvPlayer bug which should get fixed at some point (see the earlier link). Although I just tried a Region-2 DVD, and it seemed to work, strange! BTW, when we get the non-beta (final) OS4.1 for Sam440, then the bug should not be a problem either.

@xenic Quote:
*Sigh*. Is a little email too much to ask? I bet he could fix this bug in a few minutes, if he knew about it.

@wawa
Well, at least you can fall-back on your old backup.... right?

@Troels
Sad situation. Did he give any excuse, like being away from home/internet-access for not answering emails?

As far as him telling you he had started work a long time ago, but then publically saying he has only just started work - both can be true. When he said that to you, he may have meant that he was working on the MorphOS code to remove MorphOS dependencies, but he may not have actually tried porting it to OS4 until 2-3 months ago. I would not see any problem with that, APART from lack of communication about what he meant & what the progress was.

@Chris
Yes, set-up AmigaInput correctly (as far as I know), but even keyboard doesn't work properly:

For Payback 68k, the keyboard (& joypad) do not work in the menu (except fire/spacebar), but I *can* start a game. In game the fire is constantly held down, and I cannot enter any cars (perhaps because of that).

edit: Pressing Continue (instead of Ignore) just leads to another DSI error, forever.

Bah, while Nexus (Sam440) reports that he can ignore PaybackWOS's DSI exception without problem (and so can play the game fine), I find that OS4 (Sam440) crashes badly (freeze). And keyboard/joystick controls do not work properly on the 68k version

So it would be great if the DSI exception could be fixed...


Oddly enough, ignoring OWB 3.1's AddressBook DSI causes the same OS4 crash (freeze) for me, yet others have reported they can ignore it without problem. Is there some trick to ignoring DSI errors on OS4.1/Sam440?

@TiredOfLife
OWB still crashes. I do not think it is a problem with AddressBookmark, but OWB (when trying to start AddressBookmark).

@TiredOfLife
No, ignoring DSI usually crashes OS4 completely.

@PEB
Redownloaded & installed OWBAddressBook did not help at all.

Does no-one else get a Grim Reaper when using Tools/Bookmarks ?????

OWB 3.1 crashes (GrimReaper) when I start the AddressBook. It worked fined with OWB 2.20 .

@Amigamancer
Why should they add features that they don't need & that no-one asks for? I certainly wouldn't bother

edit: Plus most freeware programmers can usually do with a bit of encouragement & feedback, to know that their efforts are worthwhile (and that someone is actually using it).