@tlm

Yes, I'm using lpr.device to print to a postscript laser. Used to be a Konica/Minolta, now it's a Xerox phaser. But the printer is connected to my router, not to another computer. So it's probably a bit more complicated for you.

Paul

@Cygnused

Didn't think I'd be coming back to this thread. But a really odd thing happened.

AmiCygnix now opens in a matter of about 2-3 seconds for me. That's as opposed to 2-3 minutes or more before.

Before what, you ask? The router on my home system died. After I replaced it, suddenly AmiCygnix was working like a champ. General surfing was a lot faster, too. But this unintended and unexpected result with Cygnix is just weird! (nice weird, but still weird)

Paul

@CountRaven

My A1 is in a CoolerMaster Mystique case, with a Corsair power supply. Any case that has room for a full size ATX board should work.

I have a Catweasel Mark III in mine. It works OK. Snuffy has a Mark IV, and has had some issues with it. The "drivers" -as such- sort of work. I can read, write, and "Format" (by writing an empty ADF image) Amiga and PC floppies using my MKIII.

Cooling has always been an issue with the A1's. . . although maybe not so much for the G3's. Be sure you have an effective cooling fan of some kind for the CPU.

Make sure you start off with a brand new 2032 coin cell battery on the motherboard when you put it together. It's easier at that point than when it's in the case and surrounded by cables.

Paul

@tfrieden

Quote:

Just the fact that there are still planned updates in the silence of the court case shadow is encouraging to hear.

Thanks

Paul

@Gebrochen

Quote:

It's not consistent. Usually, clicking away a DSI with this gives an instant ISI. But last night, I was able to go on for quite a while after getting rid of a page_sweep DSI.

I've had 5 more since posting the second error log at OS4 Depot.

Paul

@cygnusEd

Quote:
Same harddware here. 512 RAM. Takes about 2 minutes for a blank xscreen to appear tonight if I click the Abiword start icon. But so far Abiword itself hasn't started.

Quote:
Using this from a shell, actually nothing happens, whether I run it from the prompt set at the cygnix directory or from the Amiga system prompt. (I've added the Cygnix stuff to the path in the startup-sequence}

Quote:
Since my first question here, I have removed everything Cygnix related (as far as I know) and re-installed from scratch. This time it didn't put ANYTHING in user-startup. I copied back what I posted above and put it in user-startup again.

BTW, that X window that came up when I started this message finished up loading the panels, background, etc within seconds of clicking on the Xami-startup script.

Was Xami part of the 1st gen Cygnix stuff? Otherwise, I don't remember installing any Xserver stuff since I tried Wolf Faust's stuff years ago on my A4000.

Paul

Sorry to be so basic here. But I don't think this was really covered in the "Cygnix . . . doesn't do anything" thread.

How long should it take for Cygnix to show its screen once the startup script is executed? Usually I get a pop up saying the X-server couldn't be started. Then some time after clicking that away, I get an X11 screen. But all it is is a crudely dithered gray (alternating chunky black and white "pixels") with no real output.

Then if I click back to the Workbench screen and execute the start Xami.bat script, it will finally bring up the actual X screen.

I have an icon out for the Abiword startup.bat script. If that's the first thing to get clicked, the process follows the same pattern described above.

So, in essence:

1. How long should it take for Cygnix to show up?
2. I just installed the 4.1 SDK in hopes it might make a difference, but it doesn't change anything in the Cygnix startup.
3. Note I have no real complaints about using Cygnix once it's running. I mainly use Abiword, and iyt's reasonably fast considering the "dual" environment setting it's running under.

So thanks CygnusEd. This is great stuff.

But is there a way to speed up the startup?

Here's my relevant userstartup settings in 4.1:

;BEGIN AmigaOS 4.1 SDK
assign SDK: System:SDK
execute SDK:S/sdk-startup
;END AmigaOS 4.1 SDK

;BEGIN Cygnix
assign Cygnix: "Programs:Cygnix"
path Programs:Cygnix/CygnixPPC/local/bin ADD
path Programs:Cygnix/CygnixPPC/bin ADD
path Programs:Cygnix/CygnixPPC/X11R6.3/bin ADD
;execute Programs:Cygnix/s/Cygnix-Startup
;END Cygnix

Paul

edited to reflect commenting out 6th line of Cygnix user-startup info. Booting hung up when I tried to do it with the "execute" enabled.

I've added another crashlog on this error. log #133. This time I was able to cancel out the DSI and keep working.

Paul

@Snuffy

Check the other thread I started on this forum. There's a link to my error log for the page sweep problem. I don't know what it is, either.But it says it's kernel related.

Paul

Please see crash log at the OS4depot crash log site, report number 131. HERE

These GRIM's are a DSI. But if I try to continue through them, they always pop up another GRIM with an ISI.

Anyone know what I need to change? Is this connected with swap memory, even though it says it's a kernel error?

Paul

@Cyborg

re: Delete "ALL"

Thanks. I've always been more of a Workbench, visual user. I thought there must be something for commandline which would function like the "Force" or "force all" option which sometimes comes up in pop-up requestors.

Now that the file system is cleaned up, I'll need to find out what's going on with GRIM's for a page-sweep error.

Paul

@LyleHaze

Quote:

They are sort of stealthy. Could be.

Paul

My A1 has been acting a little flaky lately, so I decided I'd better do a fresh backup of at least the System: partition.

I have two physical hard drives, both connected to a SiI0680 card. The smaller of the drives is partitioned similarly to the larger, which is the main drive. The smaller one is a more-or-less manual version of a mirror drive for backups.

When I back up a partition, I just run "copy partitionx: partitiony: all clone" and I have an (almost) instant backup done.

Today, It got all the way to the end of the copy process and kept looping on copying a directory called sysback. Sysback: is supposed to be the name of the name of the System (DH0:) partition when it copies to the second HD for the backup of that partition (SH0: on the little Seagate drive). I have no idea how a directory with that name ended up on the actual system partition. But it was an empty directory except for one directory entry. "Sysback." In fact, it seems there was an infinite number of directories nested under that first Sysback directory. I couldn't delete it, even from a DOS prompt in shell, because ti still showed as having some content (the empty directory.) But every one of them was identical: empty except for a directory named Sysback, holding another directory named Sysback.

Too bad I had already quick formatted the actual partition by that name in preparation for the backup process.

After booting from the OS4.1 CD, I was able to do a directory by directory drag and drop backup onto the Sysback: partition on the smaller HD, and was able to boot from it. I finally got rid of the nested, recursive directory problem by formatting the System: partition and then copying back the fresh drag and drop backup I had done.

It turns out there was also another directory on the "bad" system partition holding an entire backup of my Data: partition, too. I didn't put it there!!! I keep a separate backup partition for that on the smaller HD, too.

The problem seems to be solved now, but I'm a little concerned about how this stuff is getting there in the first place.

All my partitions are formatted SFS00 with 512 block size and 600 MB buffers. I've been running SWAP enabled on a separate, properly formatted SWAP partition, ever since switching to 4.1.

What should I be watching out for here?

Paul

@AmigaPapst

Quote:

No wonder I keep getting messages that no packets are available for OGR26. Wow! That was fast. Seemed like OGR25 took forever by comparison.

But at this point I need to clear up some problems with seemingly random ISI and "program" Grim's before I start up with dnet again.

Paul

@PEB

Tired as I was, that's entirely possible, although I THOUGHT the progress bar was not showing.

At any rate, I got the Hyperion update files tonight with OWB 3.7 and it worked without a hitch.

I saw a comment in a thread over at AW about download problems if the file is too large. But I didn't go back there yet to see if there was any clarification about that.

Paul

@Ricossa

Quote:

I tried it with the samba base.lha file at OS4 Depot last night. It looked like it worked, but when I tried to unpack the lha file after download, it complained several times about inability to access data because of corruption in the file.

The same file subsequently downloaded with AWeb worked fine.

But I only tried it once with OWB, since it was getting really late at night. So it could have been a fluke. I'll give it another try soon.

Paul

@tldaley

HOST 192.168.0.6 RAW PORT=9100

This has been working here for quite a while now.

I think the port number or descriptor is required.

Paul

@Swoop

It can be set up either way, Peter. I do mine manually because I don't always want to get the second account at home.

But there are options for auto collection at program startup, auto collection when going online, or timed auto scanning for messages while online.

I have a separate partition set up just like yout's for barious online apps, with cache for AWeb set up as Ram:. Simplemail, AWeb and OWB get lots of use here, and occassionally Thor. I've had no trouble with any invalidated partition this way.

Paul

@interrogative,

I've read that in some places, too.

I won't say it's bad advice, but I think there's a safe solution that avoids the slow down with FFS.

I threw a second hard drive in the system just for backing up each of my partitions. At one point last year, my main HD died mechanically. At that point, I just readjusted things to run everything from my back up drive, and put in the (new, free, smallish) Seacrate my son had given me, and created enough partitions to redo my backups. If it's just an invalidated partition on your main SFS boot partition, you can reboot from either your backup HD or your original CD, quick format your invalid partition, and "copy dh0: hd0: all clone" and you'll never know the difference.

Even with lots of cache allotted, the slow performance of FFS compared to SFS is just too much to take for me.

Paul

@interrogative

Quote:

Were you able to leave the partition as SFS/0 ? I hope so for speed's sake. I've been wanting to try JXFS here on some of my non-system partitions but haven't had time. But I can't imagine going back to FFS anymore.

Paul