It's nothing to do with diskboot. I get them also when I'm developing system software.

I don't know why diskboot figures in the stack trace - it may be that some filesystem needed some information from it and had to call it.

The fault is in glquake (4th line).

Never was interested in "appliances" meself. I was always a home-brew man. But these days you can't hear anything on HF because of all the interference around here. Time was I would be working in the shed at night and the Yanks would be pouring in on 20, but not these days.

I still have a good home-brew RX that was once a BC-348. These days it's a bit more clever than the old BC-348, though. With its built-in micro keeping it rock-solid on tune and decent analogue lineup, it's a pretty good radio.

But nothing beats the DSP facilities of a modern set. Just can't justify the expense.

No problem. I thought it was a virus on your site.

What's with the "System Test" popup this morning? It looks like a Windows virus, with a Close button on the right hand side.

The locks are made by the filesystem, not by DOS, although the memory structures used are allocated by DOS.

Some filesystems use a linked list of Locks, but the links are unidirectional and the start of the list is not accessible, so you can only see the "downstream" part of the list, which is not exhaustive.

You will also see everyone's locks, not just your own. There is no identification of which Processes own which Locks.

Why do you want to know? What can you do with such a list? Perhaps you want a list of FileHandles, not Locks, but these are not chained together by any filesystem that I know of.

As a betatester, you have the latest dos.library and the latest documentation as well (included with the distributed archive). The documentation should all be in there somewhere.

I don't know where the boundary between the filesystem and DOS is in this case.
You know who to call...

What you are seeing is probably related to the way that soft links are implemented (or not) in that particular file system. All the old filesystems do it differently and there is little, if any, consistency between them.

Soft links and their semantics are one of the areas we are trying to refine and define at present.

Which version of dos.library are you running?

When I was in TV many years ago we often had to clean keyboards that had had coffee spilt over them. Dried sugar on a PCB is just as bad as dried salt.

I would suggest that you remove the battery immediately to stop corrosion. Then, at your leisure, dunk the board in a bath of alcohol (we call it methylated spirit, I think it's called something else in the US). Give it a good wash - the clean water + alcohol won't hurt it. Once it's clean, hang it up vertically so the alcohol can run off it and allow it to dry in a warm place if you can. Leave it for a day or two for all the water + alcohol to dry out from under the chips, then reassemble.

If it hasn't been damaged by corrosion around the battery, it should work just fine.

SFS\00 is limited to 128 GB.
SFS\02 is limited to 1 TB.
FFS2 is limited to 2 TB minimum (can be as much as 128 TB with larger block sizes).

Hi Hitman,

The X-1000 is 1.8 GHz whereas the AmigaOne 500/Sam 460 is already 1.15 GHz (IIRC), so the speed increase is only 56%. Only! However, the X-1000 has much more expansion capability than the Sam series (takes up to 8 GB of RAM, has lots more PCI slots, etc).

The Sam 460 series is more advanced in development than the X-1000, but betatesters have the advantage of later releases of the X-1000 SW.

Currently the Sam 460 has only early versions of the built-in SATA driver and on-board audio, but everything else is done. The X-1000 has a beta version of the network driver and no on-board audio support yet, but it's in development.

Which printer driver have you selected?

@salass00:

The sampling frequency within AHI prefs is fixed at 48 kHz for the SM502. That may be why there are glitches in the transformation.

PlayCD reads one-second bufferloads of data from the CD into two buffers and swaps them when AHI interrupts to say the previous one is free. Since the clicks can occur more often than once per second, I imagine they are being generated within AHI or the driver.

The same PlayCD binary runs OK on a slower Sam 440, so it's not the app's fault.

Frankly, I find transparency a distraction and a waste of time and computing power. I have it turned off all the time.

@djrikki:

Your opinion is just as valuable as that of anyone else.

The important point is that posting the description of the bug, like this, at least gets it into the system, where someone can decide what priority to give it. Now that Andy has generated a bug report, it won't be forgotten. It would have been better on the forum, but I'm sure that Andy has included a link to this thread.

Besides, if another similar problem occurs, people might put two and two together and find it easier to fix with more information. We can't have too much information.

Quote:

You've got that round the wrong way.

"1" is HD, "2" is ATAPI (CD-ROM, etc).

Refer to the docs in Documentation/IDE/sii3512ide_dev.doc

If it doesn't get any further than the Initial CLI, chances are that your S:Startup-Sequence file is screwed or gone.

At the prompt, type "list S:" and you should see the usual suspects:

ARexx Dir ----rwed 15-Aug-12 13:08:59
Shell Dir ----rwed Thursday 11:38:00
Shell-Startup 649 ----rwed 17-Apr-11 22:23:53
Startup-Sequence 1080 -s--rwed 13-Apr-12 17:17:58
User-Startup 2101 ----rw-d 04-Aug-12 21:35:27
Network-Startup 160 -s--rwed 01-Jun-11 22:48:36

(YMMV)

If S: is missing or not resolved, "list dirs SYS:" and make sure that all your basic dirs are there. If something is missing, it might help (not guaranteed) to reinstall the Update5 over your existing system partition, but I'd go back to your clean Update4 partition, format the Update5 partition and start again.

So get a CD - any old boot CD (eg Update 1 CD), boot the system and abort the installation, go to Workbench.

Now use Notepad to edit Kickstart/kicklayout in your new installation and put a semicolon (;) in front of the line that refers to the 3dfxVoodoo.chip. Save it, remove the CD and reboot to try again.

If you like, you can put a semicolon in front of other components that you don't use - eg sii3---ide.kmod, the SCSI driver, etc. But don't go too far, just the devices you know you don't have.

Like the sound, but I detest the voice. The last thing I want to hear is a patronising American voice telling me that I have just turned on my computer.

I think you can count on one hand the number of people "demanding" DOpus Magellan.

As for writing versions for multiple OSes, that is another waste of resources. The clones have failed to take over the world, there is no point in trying to keep them going. Do it for AmigaOS only and eventually we will get everyone back into the same system.

I must be one of the lucky ones. I have only tried it on the A1 so far. I have a 1 GHz 7455 (operating at 1.066 MHz) and 512 MB of memory. I have a separate partition for Timberwolf, and I have experimented with different filesystems in that partition.

My OS is the current betatester installation. My test page is my Home page, www.abc.net.au/news. I fetch the test page by clicking in the URL and typing the address above. I run a Shell with "top" so that I can see how much CPU time the browser is using.

Using the setup just described, I have no problems starting or loading. I have not changed any libraries and each test below is with a clean install of TW into the clean, newly formatted partition.

On all filesystems tested, the CPU usage settles down to a few per cent after the start pages are loaded. As soon as I click in the URL gadget, the CPU usage jumps to > 90% and stays there until I hit Enter. If the page can't be found (due to a typo, for instance), the browser hangs with no CPU usage and the system must be rebooted.

FFS\07: Loads very slowly but works OK with test page.
SFS\00: Unusable. Loads Firefox and Timberwolf project pages OK but becomes unresponsive as soon as I type in a URL.
SFS\02: Same as SFS\00.
JXFS\04: Much faster than other FS. Works OK with test page.

The TW browser uses about the same amount of CPU time as OWB when in steady-state on the test page (RA-OWB). It's nice to see the fonts now at a normal size, but I still don't like the fact that TW, like MUI-OWB, shows all fonts as sans-serif, ignoring settings. IBrowse and RA-OWB default to serif fonts, which look so much better in a text document.