Hi everybody,

Now that SAM is imminent, maybe new developers can help with old projects. Hence I wonder....

We need a wxWidgets port... that'd open the doorway to things like Audacity, which would be great (AmiSoundEd is a nice little program but doesn't have the capabilities of Audacity (yet?)).

There must be other projects...

Is there a nice webpage somewhere describing what projects should be done? Maybe prioritising them according to usefulness. I'm talking realistic projects here, like wxWidgets or MAME rather than OpenOffice or something.

If we prioritise correctly, we can start with team efforts on small projects which will allow us to work on larger projects as the necessary dependencies are fulfilled.

Is there such a resource? If so we need everyone who has an OS4 machine to know about it, and there'll be plenty more of them now SAM is (more or less) here!

I know that wxWidgets has a sourceforge project but it's very out of date now. We need a concerted effort, a proper coding team, to get the ball rolling... maybe SAM's arrival is the kick up the backside we all needed!

Let's make it happen!

It's not really a bug per se, but how hard would it be to enable Sil3512 booting? I was under the impression the Sil3112 and Sil3512 were practically identical chips, would it just be a matter of changing the wanted PCI ID to recognise 3512 chips as well as 3112?

If it's not don't worry about it, but would be nice to boot off my SATA drive. :)

I get the same error with gmake though.. no rule to target.

This is using UNIXoid pathnames throughout, and this time the files do exist...

@thomas

Nope. I just noticed that it says "no rule to... " if the file isn't found for some reason. Slightly misleading that!

However, the problem kinda remains because I'm actually using



et al.

Because I'm using make with gcc it's expecting UNIX-like paths... so the files aren't found. Or something.

I could probably get the Makefile to find the file but then GCC wouldn't find them, I reckon.

How do people get round this?

Hi everybody,

Perhaps you can help me here.. I'm trying to compile.. something.
Anyway, I'm having a trouble with "No rule to make target ..." errors.

This is a sample makefile I copied from a website so it should be ok!



Those are TABs in my file, not spaces, of course.

I've also tried using ".cpp.o :" in place of "%.o : %.c"

It's complaining there's no rule for a .o file but it's clearly there....
Can anybody give any advice?

Thanks!

My A1 has an MSI CD-RW in it but generally everything else I have is Lite-On - they're cheap and I've had zero troubles with them. The 24x CD-ROM is a good few years old now too....

I bought a SATA DVD+RW LD drive for my A1 and it worked perfectly so I got one for the A4000 which is also fine.

You can... just be aware that there are changes so don't bother trying to do anything which uses the advanced memory features. Anything else should work just fine though.

@Swoop

That's SATA. They're identical drives... ?16 on eBay job, but so far all my Lite-On drives have been very good.

It's connected to the A4000's internal IDE via a ?0.99 IDE->SATA converter, but I'm going to attach it to the Deneb soon, for a bit more speed.

4.7GB packet-writing removable storage is nice - and just worked first time under OS4 on both machines.

For what it's worth my A1XE has a Lite-On DVDRW drive that works just fine. I actually have an identical drive in my OS4 A4000 too,
works very well!

This is the log from SFSCheck:


Partition start offset : 0x00000000:00100000 End offset : 0x00000000:80738000
Surfaces : 2 Blocks/Track : 4
Bytes/Block : 512 Sectors/Block : 1
Total blocks : 4207040
Device interface : (standard)

Checking RootBlocks
...okay
Checking AdminSpaceContainers at block 2
...okay
Checking NodeContainers at block 7
ObjectContainer at block 4315 doesn't contain node 101
...damaged

It appears to stop there though.. so there may be other errors?

Hi everybody,

First: My system, for those that don't know, is an A4000/Prometheus Voodoo III, Deneb system. The HDD is a Maxtor Atlas 36GB UWSCSI drive.

Anyhoo.. today it did a strange thing. Running AmiUpdate as usual, there was an error in the filesystem, it couldn't find a block or something, A function therefore failed, something like GetLocalTime() or something. Nothing seemed too wrong though so I didn't worry about it.

Now, however, when I boot the Amiga, I can't open System4.0:, my boot partition. Other partitions are fine. Equally, AmiDock just freezes. It doesn't respond to anything.

I tried disabling the WBStartUp and everything works ok... so, it looks like a problem with AmiDock? Hence I make a backup copy and delete it. Or at least I try to. Deleting AmiDock.info locks the system solid (and doesn't delete the file).

Reboot no Startup-sequence. Delete AmiDock#?... hangs solid on AmiDock.info.

Everything I do with AmiDock.info hangs the system solid.

When I get home I'll try to delete AmiDock itself, but I don't want to have to! What's wrong with it? The filesystem should never hang solid on trying to delete a file. It even did so under 3.9 (I dual-boot my system).

How do I fix this? This is running the latest (AFAIK) SFS filesystem.

Any advice gratefully appreciated..... but this also seems to be a bug that needs to be fixed (it should give an error - never lock the system up solid like this when accessing a file).

That's part of what I love about the Amiga community; some of it is so detached from reality there's a kind of endearing innocence about it.

Atheist, I'm sure your motives are admirable, but believe me the market has changed massively since the days of the C64.

In those days you had to get your hands dirty to use your new computer with 39KB of useable RAM, and it was capable of producing cool 2D effects and simple lo-res graphics. Those were the days of the home computer.

These days you have "next-gen" consoles pushing photo-realistic graphics around hi definition screens at full framerate with full 24-bit 7.1 sound.

Or you can buy a cheap PC for about $600 with dual core processors and comparitively ultra-fast 3D graphics at high resolution.

Ask man-in-the-street which they'd rather have: Next-Gen Console, $600 PC or a NatAmi which they can program. You don't need me to tell you what they'd say....

Why on earth would anyone apart from people like us be interested in such a limited machine? The NatAmi is great, and I look forward to seeing/owning one. But it's so far removed from current technology it'll never appeal to anyone but the hardcore.

In the past, everyone had a micro-computer because they were new, funky, simple to use and not expensive. Now everyone has consoles for the same reason, but to them the rewards are magnitudes higher with a console than any NatAmi computer could be, so which are they going to buy?

Face it, the days of the micro-computer are gone. We live in the days of the generic no-name PC and consoles, and even that's declining as consoles and set-top boxes become more advanced eventually we'll see the PC go to a minority like it was back in the 90's. Don't know about roud your way but here in Aberystwyth, the Game store has shrunk its PC game section right down compared to a few years back... that says a lot, I feel.

Personally, I miss the old days *sniff*. But that's just the way it is.

@A1200

The simple answer is that the 68010 upgrade isn't worth the hassle unless it's a quick change.

Whoever told you you get a 10% increase over the 68000 was either a salesman or very optimistic! Fact is the 68010 is basically a 68000 with a very very small instruction cache, only useful for loops of two (2!) instructions I believe. The clock speed is the same so you really won't see any difference except less programs will work, really.

That's just my experience from memory of course!

Just thought I'd report my findings....

I've been trying to run PC-Task - just for the heck of it, really.. Every time
I'd run it it'd do nothing and then the machine would lock solid whenever I did anything else like launching a new shell.

I eventually tracked it down to the locale prefs! If I change my locale to English rather than British English, it works fine!
Change it back to British English and kerblammo! one locked system.

This is probably something nasty in PC-Task but it's something you should all watch out for. Whatever happens it shouldn't take down the entire system....

@Gilloo

Just tried it now, v0.96.

Running from no startup-sequence:
I ran USBStart. (as in "Shell:> Run SYS:System/USBStart"). I had to run it otherwise it never returns.
I then ran sys:prefs/Anaiis. Nothing happened. Never returned or did anything.

Booting from full OS 4.0:
run USBStart from Workbench, can't see anything happening...
... but now whenever I click anything, the computer will hang solid. Opening a shell from the dock will hang it, running Anaiis from Prefs hangs it.

Does that help? :)

@SimplePPC

If I just load the highwayusb.device.kmod and disable all the actual USB modules, it'll still crash when I format a disk. That's with nothing plugged in at all, just loading the kmod is enough to make it crash - the mere existence of it.

I do wonder if perhaps it's getting caught up in the interrupts - loading the device will put the Highway device driver into the interrupt chain, and I presume both the disk interfaces and the Highway use interrupts too....

Don't know if it helps any but I noticed that my faster hard disk is much more prone to crashing than the slower one (when the Highway is used, naturally).

I tried lowering the disk speed to 16-bit 1MHz symchronous transfers and it became very unstable.. Put it back up to default (20MHz or whatever) and it was back to normal.

It's interesting, though, that the faster the disk the more likely to crash. The Micropolis Stinger 4.3GB 4743WS is the more stable: I copied an 83MB file to it, no problem. I then did a join to itself to double the size ("join test.vob test.vob as test2.vob") and this worked. Did the same again and it crashed.

Tried the same on the Fujitsu (10K RPM 9GB) and it wouldn't even finish copying the file before crashing.

Copying the 83MB file to the DVD+RW in the first place was no problem at all.

I'm hoping the Deneb comes out and works soon so I can try that. This is very frustrating!

I wonder sometimes if the PSU is iffy but then I'd expect reboots not consistent hangs like this. That's what bugs me most - it's so consistent....

I suspect a sound driver for USB would require isochronous transfers, which I believe no Amiga USB stack supports yet. Hence why there are no USB sound drivers.

I could be wrong though!

@whose

But if it's a hardware problem how come

a) It's only when writing heavily to a disk
b) It's only under OS4.0

With the Highway installed, OS 4 wouldn't install - it'd crash about 75% of the way through the install, even with everything else removed.
With the Highway removed, OS4 installed perfectly.

The hardware is fine, just to prove it I'm playing a DVD (somewhat slowly of course!), it's been on for an hour with no problems, and DVD playing is very CPU intensive..... but if I write a large file then it freezes pretty much every time.

If it's hardware I'd expect it to be much more random, i.e. resets as well as hangs.

It really makes no sense to me unless there's something which is just about valid on most peoples' setups but not mine. Very strange and very annoying.

My CS-PPC is an early one - serial number 72 or something I think.. could that have anything to do with it? Maybe it's the Eagle tower backplane it's on, but it all seems a little too consistent...

Either way, though, if it works on OS 3.9 there must be something OS 4 is doing which is somehow more demanding...

I did the changes you suggested and there were no changes, no useful debug output on crash. However, it did get me checking other things...

Now, I format a disk to see if it's working or not - it's the simplest way, and doesn't risk loss of data.

Without the Highwayusb.device.kmod in the Kicklayout, debug kernel:

Boot with no Startup-sequence
SYS:System/Format DRIVE hd1: name Test
Formatting cylinder 1, 2024 to go (0:00:45h remaining) [or similar]

This updates until cylinder 250. The timer counts down, but when it gets to cylinder 250, it says (<1 sec remaining) even thought there's another 1775 cylinders to go. This makes it repeat the message as it goes off the edge of the 80 column screen.
However, it carries on formatting.

Same thing with Highwayusb enabled:

Updates until cylinder 250 as before, repeats the message 10 times or whatever, says "Verifiying cylinder 250" etc.

and the crashes solid.
Just tried it again, got as far as 275 before crashing solid (which is of course the next chunk after 250).

Can someone else with a Highway do exactly the same test? My HD1: drive is a partition on the CSPPC device, but I've had the same problem on other drives (a CD-RW device).