@AmiKit

Very cool!

But what use is having AmigaOS on the phone, apart from the cool/geek factor? :)

How does it handle the phone being in standby mode, like if you have f.ex. AmIRC or AmigaAMP running? Does it run the CPU at 100% like the desktop version IIRC, draining the battery, or does it freeze AmigaOS, or run in some kind of low-power mode?

@Severin

Quote:

No, doesn't work that way. The CPU voltage regulator is very accurate and can tolerate large swing in the 3.3 or 5 or 12V input. 5V from the power supply isn't 5.00000V, it's more like 4.7~V to 5.5~V and swings wildly (in microsecond range) with the current load of the CPU. The CPU regulator's job is to make sure it deliver 1.34V at all times, if that's what it is set to.

Yeah, using composition isn't very difficult.

Maybe if someone looked at this, the memory trashing bug could be spotted too?

Currently the media player in OS4 Odyssey cannot really be used because the whole system become totally unstable after it was used with random crashes anywhere and usually system freeze some time later.

@ChrisH

Could you send me a log of the weird output from BackUp?
It really shouldn't give any warnings if all is fine.
What could probably happen is if a file is read protected, it can't read it. It could also have problems with softlinks that point to devices or assigns that aren't mounted.

Still, would be very interesting to see what files it came up with these warnings for.

@Chris

Yes, higher density put a lot higher demand on things, but it's not the same technology as 500MB disks. Yeah, sure, platters and heads, but that's pretty much it. Someone won the nobel prize in physics for some quantum mechanics discovery that made it possible to compress data far more denser than before and still read and write reliably.

Quote:

I find SSDs to fail a lot more often than harddisks (except when someone makes a bad batch, like these 7200.11 and 7200.14, and the old 20-80GB IBM DeathStar (ehrm, DeskStar) disks).

SSDs are also a lot denser than harddisks.

Oops!

I wonder what's in my X1000 as original. Fortunately I make regular backups to my second 2TD WD Green disk using BackUp

I remember when I was working as a technician at the university a long time ago and personell got new machines with IBM deathstar (deskstar ) 20-40-60-80GB in them. They pretty much all failed within a year

Old thread I know...
Did anything happen to this? Is the 68k version even released somewhere, or have to/cannot buy it somewhere? I cannot sem to find any version of it.

@Helgis

I thought the same, but designing a garage
Apparently Cycos is the right tool, but it is not very easy to use without reading the docs first.

@ddni

The serial number is in the readme on the About this release page: 548200795
Just fill in some name and this number and it will start.
I fixed the html doc which was encrypted/compressed somehow, and with nowrap html tables making it unreadable.
Cycos help

Thanks kas1e for working on Odyssey for OS4 again, and to deadwood for the hard work of upgrading Odyssey with the latest webkit! Just hope some day not too far away we also manage to get it to work on OS4.

I just bought a (slightly mouldy) house and have a kid on the way, so my programming time is basically zero nowadays :(

OS4 and the other NGs was on the todo though it seemed... Thought I might help out.

@Sir_Lucas

Cool! Maybe I can ask for source and port it to OS4 with big file support, virtual memory etc. to allow huge file uploads.

You probably need to increase the maximum horizontal frequency or pixelclock in the RadeonHD icon tooltype.
A simple calculation says the pixelclock needs to be at least 165888000 (166MHz) and the horizontal frequency 64800Hz.

Maybe that website doesn't set a proper MIME type on this file (because it doesn't have an extension) and Odyssey obeys the MIME rather than being smart and see that the image comes from an <img> tag.

@Severin

Ok. I'll find something that doesn't work when I get home. Not all combinations fail, but typically repeated use of the same options tend to not work. I have several examples where I had to write an arexx script to extract the path part and file part from {f} or DOS scripts to be able to repease the parameters.

If it doesn't add quotes, it has a bug. It should always add quotes unless told not to, with the possible exception if there is no space in the file or path. maybe the auto-quote only checks the filename for spaces, but not the path or something?

And I agree about the debug flag

@xenic

Yes, I wasn't home when I wrote the example so forgot that {u} isn't an option. But the bug is that the commandline is often not complete if more than one {} option is used.

Example (I'm not home so I make things up here):
{f} = dh0:dir/file
{F} = file
{d} = dh1:otherdir

Now use all these in an AmigaDOS command line like this:
echo "mypath={f} the file={F} output={d}/{F}"

The result in the output window should be
mypath=dh0:dir/file the file=file output=dh1:otherdir/file

But because of this bug the result is more like this:
mypath=dh0:dir/file the file= output=

-------------

If you right-click and quickly drag your mouse up or down before the menu pops up, the list scrolls (too fast), if it is longer than the display. This is a very practical feature that DOpus4 also has, but in Magellan it is too fast on hi-res screens because it probably calculates how fast to scroll based on pixel distance (which is much greater on hi-res screens).

Another bug report:

The "right-click-and-drag-in-lister-to-scroll" is way too insensitive. It scrolls so fast it becomes useless. it should be a lot more gradual. Now it is difficult to make it start to scroll, but then it scrolls too fast. We have high-res screens now, so the algorithm needs to take this into account.

@kas1e

Bug report: (since I can't seem to get into source-forge)
Using multiple placeholders in a custom function doesn't work.

Example:
Create a button or menu item:
Edit action:
AmigaDOS: sys:dir/some_exefile -file {f} -dir {d} -out "{d}/{u}"

It is not possible to use more than one {f} or {d} or whatever. If I use more than one it just simply doesn't work (most of the time). They are empty or the command line is incomplete or whatever.

Test with for example "echo {f} {d} {u}" or other combinations and "Output to window". Some combinations work, others not.

Something in the parse routine for this command line string here is just plain wrong. I can have a look at it, but I can't install the build environment and the version control crap and what not. If someone could give me the file(s), I can fix it anyway and someone else can check-in and build.

How difficult would it be to move the Amiga changes over to the latest Firefox sources: 42.0?

Would be cool if someone was able to "make a leap" with Timberwolf on Amiga

@thellier

Are you on 68k or PPC?

68k uses 80-bit floats internally. Not sure how the compilers implement double in this case. I think x86 also uses 80-bit floats, but PPC and probably x64 uses 64-bit floats.

I rarely use a word processor, but when I do I typically use Word Online. Pretty slow but it works, and I can print it at work without even needing to email the document anywhere.

All that's needed is a hotmail or live.com email and you have it in the top-left corner. You've got excel and powerpoint in there too.

Many years ago I used FinalWriter. Of course a native program is better, but this Word-in-the-browser is good enough for my needs now.