@Bill E: Hyperion certainy does NOT have a bias against Ibrowse and is even shipping an OEM version of Ibrowse with AmigaOS 4.1.

The idea that Hyperion would intentionally corrupt files for download by Ibrowse borders on the extreme paranoia.

If Ibrowse were no longer supported, users would be informed of the fact and certainly would not be subjected to deliberate corruptions of downloads which would be highly unprofessional.

_________________

@Hyperionmp

Can this version be used with AOS4.0 final? If not, which version should I use?

_________________
PowerBook 5.2 MorphOS 3.15
PowerBook 5.8 MorphOS 3.15
Amiga 1200 BPPC/BVision AOS4.1 FE

@emeck

Are you asking whether the SDK can run under OS4.0 (yes, of course) or whether binaries compiled under this SDK will run on OS4.0 (mostly, but some components will expect OS 4.1 libraries, etc).

If you are building binaries to run under OS4.0, you might do better to stick to an older version of the SDK.

_________________
cheers
tony

Hyperion Support Forum: http://forum.hyperion-entertainment.biz/index.php

@tonyw
Quote:

If you are building binaries to run under OS4.0, you might do better to stick to an older version of the SDK.

Yes, that's what I need now. I would like to start coding with my recently revived A1S3 which has AOS4.0 final, until I can upgrade to 4.1

So which version would be the best?

_________________
PowerBook 5.2 MorphOS 3.15
PowerBook 5.8 MorphOS 3.15
Amiga 1200 BPPC/BVision AOS4.1 FE

@Zerohero:

Have a look into /devices and /libraries directory within include_h. I compiled a project today using AHI device functions, compiled fine and works (I compiled it with CodeBench, btw.). IIRC the proto files were missing from the beginning, I remember that I had to copy over some files, but Im not 100% sure if it was proto/ahi...

@Hans

Quote:

Do you know of any tool that could be used to create an update that patches the old archive?

There's xdelta3 which is very efficient, but it really depends on the difference between the old and new file.

If you make an ISO from a file list and then add/remove/update a few files and recreate the ISO in the same order, the differences are likely to be minimal, resulting in a very small xdelta file, however with compressed archives like the SDK, it's less likely for the resulting binary to have anything in commun with the previous one so it would be more effective to compare the files and only pack the updated ones in a new archive, though that would take a lot more work.

But here we're talking about an 80MB file, how long can it really take? Even with dial-up that's at most 4.5 hours at 5KB/s, so either Bill is paying to dial out and would be better off having someone mail him a CD or it's only a matter of starting the download before heading to work (or the pub ).

@BillE
I had to download each beta version of that SDK before its release and with my connection it still took 30-40 minutes each time, not to mention inspecting every single file inside the archive to try spotting potential issues (though it seems I missed a few), so consider yourself lucky

[edit]
I downloaded the sdk 53.15 archive with IB and indeed it was corrupted, with an extra 72 bytes of data on top, ironically it's the html from the warning about using IB/AWeb:

<font size="+1" color="red">Warning: We discourage the use of IBrowse or AWeb for product registration</font><br>

As a result the UnArc utility can't open the .lha file, but the lha command still extracts it fine by skipping the extraneous data.

I also tried creating a diff betweeb the 53.15 and 53.20 updates with xdelta3 and the resulting file is 20MB, so it's not a huge gain but it's something, and it requires having the original 53.15 archive to turn it into 53.20.

I can understand Bill's frustration with the corrupted downloads though so I'll look into it and see if I can help Hyperion solve it on the server side.
[/edit]

[edit]
Meanwhile, one can use 'wget -O SDK_53.15.lha URL' with the URL being reconstituted from the javascript download link.

Even if I enter the direct download link into IBrowse it still gets the extra 72 bytes prepended so I'm starting to get a pretty good idea where the problem is.
[/edit]

Last edited by AlexC on 06-Mar-2010 at 02:53 AM.
Last edited by AlexC on 06-Mar-2010 at 02:34 AM.

_________________
AlexC's free OS4 software collection

AmigaOne XE/X1000/X5000/UAE-PPC OS4 laptop/X-10 Home Automation

@emeck
Quote:

Can this version be used with AOS4.0 final? If not, which version should I use?

Yes you can however not all of the tools may run since they could require AmigaOS 4.1 Update 1 as a baseline. For example, shared objects do not work correctly under 4.0 and neither will Python (which requires shared objects).

_________________
ExecSG Team Lead

The devices/ahi.h file is there but everything else is missing. All the handler autodocs are missing (removed?) which might be inconvenient if you are cross-compiling and don't have the OS 4.1u1 user docs readily available. The "textclip-handler" autodoc is missing from the SDK and the update1 user docs. Is that feature being eliminated?? I also notice the Printer examples and Tutorials are gone, so I guess there are no plans for new/updated printer drivers.

_________________
X1000 with 2GB memory & OS4.1FE

Am I the only one having problems compiling MUI apps with this SDK release? The MUI includes wasn't in the path at all, but there were a separate MUI directory which had includes which I copied to the include_h directory, but now I get this error:

/SDK/include/include_h/interfaces/muimaster.h:30:21: error: muiprog.h: No such file or directory

Can't find that file anywhere...

@ssolie

Ok, thanks. I had an error installing it yesterday but it was because I forgot to install first july 2007 update for AOS4.0. This time no errors with the installer.

_________________
PowerBook 5.2 MorphOS 3.15
PowerBook 5.8 MorphOS 3.15
Amiga 1200 BPPC/BVision AOS4.1 FE

Great news!

But as Bill E says, I could also use an updater since it is just so tedious to make a fresh install and then having to pick the pieces from the old install and try to make everything work again. I have no problem with large downloads though.

But then again, perhaps the time it better spend on OS4 than on some updating installer thing that might not work in the end after all... ;)

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.

@Xenic
The AHI includes were excluded by mistake. The handler docs are moved to SYS:Documentation and never belonged in autodocs. The printer examples were removed because of age. No features are being eliminated.

_________________
ExecSG Team Lead

@AmiDog
Don't copy files around please. Use your compiler options instead like -I/SDK/MUI/C/Include

_________________
ExecSG Team Lead

@ssolie

Still it doesn't explain why all previous SDK's could compile MUI apps out of the box, and it wouldn't make a difference since there's no muiprog.h file anywhere. Unless something went wrong when I installed the SDK, which is why I asked if it works for anyone else. I've gone back to the previous SDK for now.

@BillE

Just to rub it in, at my wife's place in Nakuru (Kenya), we get 3.6Mbps 3G.

At my current home I have symmetrical 10Mbps FTTH.

And at my fathers place I'm on Edge/GPRS. My next home will be in a house on his farm, and in that house I DO get 3G, for some reason. Just not in HIS house.


Anyway: Woooo! SDK!

_________________
This weeks pet peeve:
Using "voltage" instead of "potential", which leads to inventing new words like "amperage" instead of "current" (I, measured in A) or possible "charge" (amperehours, Ah or Coulomb, C). Sometimes I don't even know what people mean.

Quote:

If you are building binaries to run under OS4.0, you might do better to stick to an older version of the SDK.

Is there a recommended SDK version for 4.0 development?

_________________
All glory to the Hypnotoad!