@Thom:
Quote:

I wasn't asking or expecting that you would import OWB-format bookmarks. I am quite prepared to edit the file myself (it's only an ASCII list), but I don't know what the required HTML format is and RC1 does not (here, anyway) save any bookmarks of its own, that I could Export.

Perhaps someone with working bookmarks could export an HTML file and post part of it so that I could copy the format. Just the header, trailer and one or two items from the middle would be enough.

I'm running TW on an A1-XE with a beta installation. This is a clean installation of TW into a clean SFS\02 partition.

@Severin:
Quote:

It won't work for me, either. For me the button is always ghosted. It was in all the previous versions of TW, too.

How can I import my bookmarks from OWB? I assume that I have to edit OWB's text file into an HTML file, but what format does the html file have to be? Everything I have tried so far is completely ignored by TW.

I tried to bookmark a couple of pages so that I could export the bookmarks.html file and see its format, but nothing happens when I select "Bookmark this page" or type Ctrl/D. Exporting bookmarks does not generate any file.

I saw someone mention F11. Is there a document somewhere that describes the shortcut keys?

Is there some documentation for the GUI? What do all the toolbars do?

Are we going to see a "proper" Amiga-style menu? The current menu that shows different things depending on whether you press the LMB or RMB is confusing.

Should I be able to change the font size? The default font used throughout the GUI (labels, titles, etc, not displayed text) is much too big and ignores the system Font settings.

The first time I tried it, I had a shell open before I ran TW. After I quit TW, I tried to close the Shell and the system locked up. Unfortunately I didn't have my serial terminal turned on at the time and, of course, it hasn't happened again.

Is there any way that I can retrieve the password that I forgot many years ago?

Username = tonyw

I would be grateful if an OS4Depot mod could either mail me my current password or help me to set up a new one. I can't see any way to do it on line.

@xenic:

What version of PlayCD do you have? The original V53.6 had that problem, but it was fixed in V53.7.

G'day Allan,

What is that printer driver "PhotoSmart"? I see nothing of that name in the OS4.1 printers list.

Or are you looking at TurboPrint drivers?

I don't think that model is available out here in Oz. Nothing like it on the HP website.
It's an inkjet? Not a Laser?

What model number would that be?

@Hans:

Yes, you can boot from SFS\2 partitions.

Breaking up the disk into smaller partitions, each dedicated to a particular set of data, is good. Making duplicates of everything is essential (preferably on another disk drive).

Cramming everything onto the system partition is bad, no matter how big it is.

As an example of a minimal set of partitions:

2 GB: SWAP partition.
2 GB: System partition (OS only).
2 GB: System backup (OS only).
x GB: Programs (applications, games, etc) as big as you need.
x GB: Backup for Programs.
y GB: User data (email, correspondence, downloads, whatever). I use several partitions for this and another for photos.
y GB: Backup for user data.

Remainder: spare space (don't break it up into partitions until you need to).

etc...

USB cable/connector has four wires. Two of them (Red and Black) are simply +5V DC and ground. The other two (Green and White) are the two signal wires.

The DC and signals are not mixed, they are separate. The signal wires (White and Green) carry information in either direction, using a balanced transmission method.

USB uses a question-and-answer protocol on the bus, unlike PS/2, which simply sends data blindly.

You would need something intelligent to convert from USB to a DIN connector, but it might work with a USB-PS/2 and then a PS/2-DIN adaptors.

It's so much easier and cheaper to throw away the old keyboard and buy a new one. A good quality Microsoft-branded wired keyboard costs only $20, including a new wired mouse as well.

I don't think paste (into the URL space) is supported yet in TimberWolf.

The random picture on the front page is currently showing "http://www.amigans.net/modules/myalbu ... o.php?lid=245&cid=4", which is a screen shot of an early beta version of Sam software with display glitches.

Since this problem was only in the first beta release and was fixed years ago, I can't see any point in keeping it in the database, for possible display on the site's front page. It can only give a curious onlooker the wrong impression.

I would ask for it to be removed, please.

What exactly do you want again?

++

They are bloody noisy, too. The fan in the base sucks air in through the cylindrical stand, then blows it out axially around the periphery of the ring.

A friend showed me one that he had bought. I wasn't impressed by the noise or the volume of airflow.

My impression was that a slowly-spinning fan with large diameter blades would have done the job a whole lot better and more quietly, for the same electrical input.

Hey, ace!

Good to see you around!

Sorry, can't help with PGS.

I'm sorry, belxjander, but most of what you said in that post does not apply today and has been obsolescent for the last ten years. We are talking about OS4.

The OS4 kernel restricts memory allocations to the 2GB limit, for the reasons already stated. I would be willing to bet that the system would still boot normally if we suddenly moved everything above the 2GB barrier (ignoring the fact that we still need access to the zero page). If we allowed memory allocations to cross the 2GB barrier, some stuff would work and some would not.

As to the task of changing from 32-bit to 64, it's not dissimilar to the task of changing from signed 32-pit pointers to unsigned. Someone still has to go through every line of code in every source module in every OS component, checking for side effects. If you are going to edit int32s to uint32s, it's easier to edit them all to APTRs. The real work is going through the code, finding all the places where something special has to be done. Once the naive assumptions in the code have been fixed, you can start the fun job of debugging it all over again.

The fact remains that we have better things to do at the moment.

We can already address > 2GB. The only limitation at the moment is that the kernel deliberately won't generate addresses > 2GB (because we don't know what will happen). That restriction has to be removed at some point so that we can find all the places where things go wrong. There are bound to be some.

I don't know how big a change it would be to enable 4GB throughout the kernel. But is it worth the effort? It might be not much more difficult to rule the line under the current architecture and change everything to 64-bit in a new fork.

Or even reuse some of the immense amounts of energy that NASA used to get some of that moon junk up there. All wasted.

Quote:

No, it's changing (the potential energy that the water has at that height) into electricity. Somehow the water got up there by someone or something doing work on it (lifting it). You are just getting that energy back.

"Gravity's pull" is a constant force. You can't get energy out of it for ever, sooner or later you will reach the bottom of the hill (or well, or mine shaft).

@LiveForIt:
Are you sure about that? I can't think of any examples where a pointer with sign bit set means anything special.

In many DOS calls, pointers have to be converted into BPTRs by ( >> 2). If the original pointer is > 2GB, it has a sign bit which is maintained during the shift. Now there may be some functions in DOS which don't check that the upper bits are zero and which would fail for that reason. I'm only guessing.

On the other hand there are many structures defined like this:
Quote:

Now fh_Pos and fh_End are set to -1 when undefined (when the file is not open). To use the whole 4GB address range, we would have to replace those int32s with a uint32 and a separate "invalid" indicator. Otherwise we would have to limit the available address space to (4 GB - a few values).