The correct host is .

hmm .. so do I need to wait for webdav-handler or can I mount my WebDAV share with the http-handler as well? If the latter, what is the point in webdav-handler anyway?

Sorry, I'm a bit confused now about the purpose of those.

Ahh... there it is!

I was only looking at Open Amiga, saw the beta flags and didn't know it was released for all this years! :o

Well, great! I'll give it a spin tomorrow... need to do some BBQ now :)


Thanks!

Are there any news about this? The last beta is 2 years ago, but I saw in the SVN log something about a v1 release commit in March this year?

Hello,

is anyone in touch with Glenn Hisdal? He wrote a few tools and stuff for OS4 some years ago (AutoDocViewer, some libs, an alternative GUI to STRICQ, etc.). The email and web addresses I found are all long dead already and my try to contact him via facebook (if that is actually him) was also not successful yet.

So, if anyone knows Glenn and how to reach him, please tell me... or tell him to get in touch with me, either way is fine :)


Thanks!

@ kas1e

As Minuous implied with his question and myself with my answer, the way to identify a certain AmigaOS release is by checking the version and revision of version.library. That's the only viable and supported way.

Of course you could check for some other components known to first arrived in a certain AmigaOS release (like BOOPSI classes or so), but that's dangerous as users are much more likely to fiddle with any other component than version.library.

Update 1: 53.2
Update 2: 53.3
Update 3: soon :)


But noting the different versions in the Autodoc seems to be a good idea, so I'll record this as enhancement request for hopefully the next SDK.

@Amigo1

Huh? Never heard about such a problem and also works fine here.. I tend to always have the DevCD in the drive and only remove it if I need another CD and of course the DevCD icon vanishs as soon as I eject the CD...

Can you try to boot from the install CD and check if there's the same problem? It may be that the icon of the install CD itself won't vanish as it is the boot media. But any other CD icon should show/vanish when you insert/eject the CD.

If that works, something in your current installation is broken.

And if it doesn't work, then I would try another CD/DVD drive .. I'm by no means an expert, but maybe your specific CD/DVD drive sends a somewhat uncommon eject "message" which isn't undestood or so.

In any case, you have to do some more tests to nail down the exact reason..

@magic

Seems the designer is a Tron fan


*sigh* If we'd only have a billionair in our community...

@salass00

Quote:

Wrong!

"assign something: dismount" just removes the device entry from the system list, but does not shutdown any filesystem/handler nor free any ressources.

For that the dedicated C:Dismount command exists in OS4.

Check the provided documentation for those commands.

@kas1e

Wherever you got that "umount" command from, it was for sure not part of AmigaOS but some 3rd party tool - especially on OS3. AmigaOS never had a "umount" command.

OS4 has C:Dismount for that purpose.

(Don't confuse this with the DISMOUNT switch of C:Assign.. that switch is NOT dismounting a filesystem... check "help dismount" and "help assign" for more info)

@billt

You misunderstood. Each stack of any BSD variant supports all the modern features like IPv6, net80211, Jumbo frames, etc. OpenBSD did just not change the stack as radical as eg NetBSD and has more reliability, stability and portability in mind than the others (which partly aim for the best performance and to support new standards as soon as they wer specified or even earlier as drafts).

Regardless which BSD stack would be the base, we would get any important features introduced to the world after 1994.

Your feature wish list has indeed some flaws:

Things like "Bluetooth tethering" do NOT have anything to do with the TCP stack. First you need a Bluetooth stack, then you can write network drivers which make use of some Bluetooth devices. Just like it is now already with USB. Bluetooth is just another transport media.

The rest of your feature listing are mainly driver issues and not directly related to the TCP stack itself. (besides parts of modern WiFi support which is provided by the net80211 WiFi kernel. But even then, proper drivers have to get written which make use of it)

Also You tend to forget the manpower needed to properly do a new TCP stack which also involves specifying a whole SANA API to support very high data rates, the specialities of WiFi, etc. This manpower is not available at the moment. At least not in the OS4 team as we have already many other things to do on our desks (besides having some real life and earning money).

@Hans

Actually it's on my TODO list since a couple of years already. But there are that much dependencies and pitfalls involved that my little Amiga time is not even enough for doing serious research.

I think this task would be similar enormous like doing a whole new Picasso96 replacement, which should give you an idea about it as a graphics driver guy.

@ jbni

I'm using ch_nfs from the old AmiTCP package. Just download the demo from Aminet, ch_nfs is in there.

The sources for ch_nfs are meanwhile open source on sourceforge, unfortunately some important parts are lost and the project (IIRC its called aNFS) is stalled

@Hans

That very much depends on what you want to achieve. If you want an as robust and reliable as possible stack (i.e. "conservative"), you would probably choose OpenBSD. If you want the very latest and most innovative features, you'd probably choose NetBSD... and FreeBSD for something in between.

I think the OpenBSD stack would be also the one most similar to the BSDlite stack and hence to Roadshow.. but in the end of the day it probably doesn't matter which stack you choose as all changed so much since 1994 that you couldn't reuse much of Roadshow besides parts of the AmigaOS library stuff. And of course would any modern BSD stack support anything we can just dream of now..

And there's the documentation problem: None of those modern stacks is really well documented. Pretty much all books about the inner workings of TCP stacks are talking about some BSDlite version and really outdated. Again, the OpenBSD stack would probably be the "easiest" choice because of being the most similar stack to BSDlite.

You want to volunteer?

@logicalheart

First of all: I know the difference between MB and Mb(it) very well, so you can take my figures just like I wrote them. And I also know that it should actually be "MiB" instead of "MB", but thats something I'm not able to get comfortable with :)

As I said, under very special circumstances I got a peek of 25MB/sec for raw TCP transfers with a Gbit card. "Raw" as in "no other protocol overhead like FTP, HTTP or thatlike involved" and also without using any massstorage devices but only from/to memory.

Thats very likely the best we can squeeze out of our current TCP/IP subsystem. In real usage, it boils down to 10-15 MB/sec (e.g. FTP from/to your local harddrive).

With my 100Mbit cards & drivers (the Realtek 8139 ones) I'm most of the time between 7 and 9 MB (including any overhead) and >10MB with raw TCP transfers (which are otherwise unfortunately useless ;) ).

That is on an A1 XE G4 @ 1GHz btw.

The actual transfer rates also highly depend on the other side as well as the cabling, the connection and the used software. E.g. AmiTradeCenter is slower than pFTP probably because emulated 68k vs. native PPC (or Pete's coding skills ;) ), and Samba is slower than NFS due to the massive SMB protocol overhead, etc.pp... you got the idea.

Edit: Oh and I totally forgot to mention the Roadshow settings. The stock settings are somewhat "conservative" (better safe than sorry). With more aggressive settings you should be able to get beyond your 6MB/s ... see the RoadshowControl documentation.

@jbni

Any Realtek 8169 card should do.
But be warned: You will not get any transferrates beyond 20MB/sec .. and those only in some very special situations. Most of the time you will very likely stay at 10-15MB/sec ..

Especially with the available public 8169 driver. My current development version is a bit faster (max. around 25MB/sec), but also only in very special situations.

This is not a problem of the driver itself, but it's caused by our current network architecture which was designed with 10Mbit or at most 100Mbit in mind. Roadshow is based on BSD4.4lite (IIRC) which was released in 1994. Also the SANA2 specification for network drivers isn't prepared for such high transferrates.

To make good use of 1Gbit we'd need a new TCP stack based on modern BSD network kernel as well as an updated SANA2 specification (or even a completely new SANA3), which are aware of such high rates and accordingly written (i.e. avoiding memcpy() whereever possible, making use of DMA capabilities of network chips, support for jumbo frames, etc. pp.).

So for now, there's (unfortunately) practically no sense in using a 1Gbit card with AmigaOS only. Of course, if you are also using Linux on the same machine then you can make good use of 1Gbit at least on Linux and it will also work - just slow - on AmigaOS.

P.S: No, we don't have the resources right now to tackle this problem.

@gerograph

As it is your very own site, you very likely know pretty well whats going on and what the site is all about.. you just want to tease everybody

@vox

Regarding os4welt.de:

The prior owner/admin mash told us some weeks ago that he isn't interested anymore in running the site. So after a bit of discussion we agreed that I shall take over the site and move it to my server.

Mash then contacted me and asked me to get in touch with him via email to get a snapshot of the whole forum and sort all domain moving things etc. Unfortunately that was 1 or 2 days after I went into holidays, but I told him (by using my mobile to write the PM) that I'll get back to him as soon as I'm back.

I did that last week (os4welt was still working at that point), but the mail addresses he provided me with didn't work. So I tried to contact him via PM on os4welt, but he didn't react. All of a sudden os4welt was shutdown then, so I tried to find another way to contact him and actually found out his mobile phone number. But he didn't take my call and didn't react to my message on his answering machine nor to the SMS I sent him.

So from my side I did everything possible to rescue os4welt as it was a small but really great german forum, but if mash doesn't (want to?) react to any of my contact tries, there's nothing I can do... Really a shame to lose it

@ZeroG

Quote:

Indeed. I totally forgot about investigating gtlayout.lib further to ensure that everything is working and to release a fixed version... Olaf unfortunately doesn't seem to have time to do it himself..

Thanks for the heads up.. noted on my todo list.

@ Futaura

Of course if the nonworking filetransfers are the only thing which prevent you from using Term and if you badly need it, please drop me a PM with your email address and I'll send you the patched gtlayou.lib ... without any guarantee that it will work 100% reliable of course.

@ktadd

Quote:

Yes, it's supported.

Quote:

The driver works here in OS4 already. It just didn't make it to the fair in time.

Quote:

Like seen on the pictures of the mainboard from january already...

Quote:

Please keep in mind that those were prototyp boards. So basically everything of them is subject to change and might not be the same in the final version. But yes, the CPU stays fairly cool.

@Chris

Thanks for the report.

Confirmed and reported.