Accessing Google’s Cloud Drive for Classic Amigas

There is a tool out now called AmiCloud, which I intend to test one day soon, but that is a paid service. Last week, I saw a video on Youtube showing a new “Google Drive Handler”. This would mount a drive called “GOOGLE:” and you could access the files on your Google Drive account as if it was a local volume.

This morning, the first beta version (0.4) was released to Aminet, and I had to do a quick test. The free version is read-only but a quick 10 Euro registration fee will open up the ability to write to the cloud, use Google’s cloud print and eventually Dropbox.

First, get the file from Aminet. There is no installer, so the quick way to install is just 3 steps:

1) Extract the Google folder from the archive, and put it in the DEVS: folder.
2) Get your Google unique handler ID and copy to a file
3) Assign and mount the drive in User-Startup

The first is relatively simple. When done, you’ll have a path like this Devs:Google/

For the 2nd step, you have to follow the link in his readme:

I had to do this on a Windows machine. When prompted, I had to log into my Google Account. This presented me with this option:

Clicking Allow then presented a very long string under this text:

On my Amiga (A WinUAE session in this case, running OS 3.9), I had to open up the file: Devs:Google/_client_code using a text editor and manually typed in the long string (over the default message) and saved it.

I then added this to my S:User-startup file:
;BEGIN Google
Assign SSLROOT: Devs:Google/.sslroot
Mount GOOGLE: from Devs:Google/google.mountlist
;END Google

And restarted. While Workbench was starting up, I quickly went to and downloaded a new wallpaper, resized it for my needs and uploaded it to my Google drive on Windows side:

When Workbench was available again, I started Directory Opus 4.16, and I noticed nothing different on the drive buttons:

so I typed in Google: directly into the drive path bar on Dopus, and after a moment, I saw my Google drive file:

(The one I want is the one not blurred). I copied it to my Amiga side, then closed Dopus and saw a new drive appear on the workbench:

Double-checking, I restarted Dopus and saw the drive on the drive buttons:

And just like that, I had a new wallpaper by transferring via Google Drive.

Well done to the authors of this handler! I can’t wait to put it on my Amithlon machine!

Quick test for comparison

Okay, a few months ago, I’d heard that deadwood had released version 1.25 of OWB for AROS. Since then, he’s opened up the source and improvements have been rolling out. While I haven’t grabbed the latest version, I did want to do a comparison between 1.25 and the 1.24 used on MorphOS (since I recently upgraded to MorphOS3.9 on my Powerbook G4).

I was expecting the 1.25 to score higher than the older 1.24. However, if you look back at my last article here, you’ll see that it only scored at 362 out of 555:

At the time, I thought that was good considering that Amiga browsers tend to be way behind the rest.

To my surprise, the older 1.24 OWB from Fab on MorphOS scored much better, at 422 out of 555:

So, next step will be to updated to the latest build from the open github dev version of 1.25 and try again.

Happy New Year Amiga users!

I hope all of you Amiga users have a great New Year!  I just noticed that someone is spreading a partial archive of the old OS 3.1 source code around but that its also the same one that was around over 15 years ago.  I guess torrents make it easier to spread these days.  Will something come of it?  Probably not.  Olaf Barthel talked about the years of work it took him to get a full archive (which isn’t even part of the leak) to build under common tools, as the old archives required many different compilers and assemblers to build.  Also, how much is in assembly?  Hyperion has been working for years to convert the old code to portable C. Anyway, it was interesting to hear about.

Anyway, I’ve also recently seen a sneak peak of the new AmigaOne x5000 running OS4.1 with some nice software demos:

I’ve revived my interest in Amithlon, in my opinion, the only way to run Classic Amiga if you don’t have real Amiga hardware. I’ve built a few machines this year, with various hardware, and varying results. I hope to one day build the ultimate Amithlon machine with a wicked-fast processor speeds and start porting code to it to take advantage of the x86 raw power. Maybe in 2016?

Anyway, I’ve seen several cool thing both in software and hardware that I have backlogged to post about, so hopefully, I’ll get to them soon too.

2015 was awesome, 2016 should be more so!

OS 4.1 Final Edition Classic finally available for download

When WinUAE started supporting PowerPC accelerator emulation, it wasn’t long before Support for AmigaOS 4.1 support was added.

Not long afterwards, Hyperion released the Final Edition of OS4.1 and lowered the cost to just 30 Euros. However, it was still physical media only, with no option for download-after-purchase like most other Operating Systems.

Cloato updated their Amiga Forever system to include the new PowerPC functionality, and just recently announced that they are now offering OS4.1FE for Classics available for download (SAM and other platforms not offered).

Check it out –> here <–

New Amiga OS hardware

So, currently, we have ACube’s SAM460cr and A-Eon’s x1000 Nemo board that came be purchased today. We’ve heard that the x5000 from A-Eon is on the way as soon as Amiga OS4.2 is fully ported, and Individual Computers will be releasing an Amiga 1200-ish replacement motherboard.

Add to this the variations of FPGA implementations, but the real big news this past weekend was the joint effort between A-Eon and Acube to release a new, mini-ITX motherboard for Next Gen Amigas tentatively called the “Tabor”, or the A1222. Rumors are that it is based on a different line of PowerPC processor called P1022.

If this is true, then we can find out some info online about it. The P1022 is a dual-core (dual e500) CPU cores. These are 32bit processors (not 64bit). The max speed is 1.2Ghz in speed. It also is an energy efficient design with some IO controllers built-in. Some have pointed out that the FPU is incompatible with those used in other Amiga NextGen processors. This leads to the question of if there will be recompiled versions of code or software emulation if this is the case.

Why was this processor chosen instead of one that is more compatible? Probably costs. They most likely either had a good deal on that processor for this project or another project enabled them to buy extra units for the Amiga boards.

Here are the early pictures: