So far most things seem to be working well with the update.

I do still get strange lockups with the mouse which then need to time out, I had them with the previous OS 4.1 though and wonder if it may be hardware related ? USB mouse.

Anyway one big problem I do have is with Wordworth 7 which I did not have before. It generally works, and I can use it but when I try and open one particular window the A1 totally locks. A warm reboot is not possible and the computer needs to be cold booted from the reset button ot by turning on and off.

This happens when trying to open the Postcript Setup window from the Print Setup window. The wndow cannot draw one of its gadgets for some reason and the lockup occurs with a partially drawn window.

It would appear to be at Kickstart level and not due to missing libraries not copied etc. I tried going back to earlier versions of the OS (but using the new kickstart files) and I still get the same lockup.

Any ideas, even if only telling me which kickstart module I need to revert to an older version ?

Last edited by BillE on 06-Feb-2010 at 11:28 AM.

@BillE

I dont think that your problem is kickstart related in any way. Most likely it is some printer related property that is causing your trouble.

How I could say this? Well, I have WW7 working here on 4.1 Update 1 and I use a PostScript printer. Even more hard: its a network printer

I just hope that this problem doesnt result from a printer or other property you have to change in WW7 itself, else a reinstall would be needed.

But I couldnt be of help with this, as I didnt experience such a trouble before or yet, Im sorry.

@BillE
hello,
have you installed the last offical update from ww (7.01)?
have installed any unoffical updates?
do you use any printer-manager and have you the same problem with other applications?

_________________
Sam460ex, Sam667Flex, CDTV, A600 und CD32
Amiga User since 1987

@whose

Quote:

Most likely it is some printer related property

No it has nothing to do with printing, I can print to a postscript file.

The problem is if I ever need to change the Postcript Settings, the crash occurs on opening this window. As I said in the original, it is some gadget related thing - the winodw only half draws before the crash, and it worked perfectly prior to installing the update.

Try it, press RA P to start a print, then click Setup, all fine so far.

Select the print method Postcript which enables the Postcript button at the bottom. Click that button and then you will see where the crash occurs - or not. It happens 100% every time here

I normally use the normal printout method but do use postcript to print to a file when creating PS and then PDF files. AT the moment I can print to a file as it was already set up, but making any changes to the postcript settings eg. printing to PS: if I want to print a postcript file to the printer and I cannot do it.


Bill.

@BillE

Just a thought did you remember to intsall the postscript handler for PS:

I have no issues with wordth7 nd postscript window here, and I always use PS rpinting from wordworth, so I would notice an issue if there were one. (Ofcourse I'm using a SAM that might make a difference, but I would be suprised.)

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@BillE
hello,
no crash when i use the desribed way.
i use a samflex.

_________________
Sam460ex, Sam667Flex, CDTV, A600 und CD32
Amiga User since 1987

@BillE

Yeah, I did what you say, but it doesnt crash here. So I think that it has to do with the settings you chose. Maybe some special handler that is missing?

I really tried hard to make WW7 crash here, but it works like a charm, no crashes at all. Some graphical glitches when using the drawing functions, but no crashes. All I did after Update 1 was, to restore all font files and libraries and ENV: entries of WordWorth.

Do you use a parallel port printer or a usb one? Did you check the Workbench printer settings, too? WordWorth uses them, too (I believe they are used to get the initial printout parameters, page sizes and such).

@BillE

perhaps you can take a photo to show where it freezes?, might give a clue....

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues



Quote:

Just a thought did you remember to intsall the postscript handler for PS:

Probably. But that is not the issue.

It is WW7 that crashes, if I wanted to select PS: rather than send a file to ram:output.ps, I cannot change it as the window that does this crashes the system

I can probably use PS: with IBrowse etc. no problem. I just haven't need to yet.

I guess PS: will work fine, I just cannot select any Postcript settings from within WW7

@broadblues

Quote:

perhaps you can take a photo to show where it freezes?, might give a clue....

Good idea, I was wondering how to get a screengrab - which of course is impossible as the system is locked up.

[edit]
I have now rebooted as to get the photo I had to let my Amiga One crash big time.

Here is the photo of
WW7 crashed.

Note how the window is half drawn, I am sure there is stuff missing from the top of the window, but I canot recall what now nor can I ever get to see it

The gadget for where to send the output to is certainly one of the missing areas.

Once I get to this stage there is no other recourse but to restart the Amiga One from scratch.


Bill.

Last edited by BillE on 05-Feb-2010 at 10:23 PM.

@BillE

The top section hasn't rendered as you say, nor the borders rounds the bottom section.

Can you post your wordthworth prefs file? Then I could try and see if that creates the crashed.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@BillE

Hmm - sometimes only parts of the OS crash/hang (i.e. only Intuition, input.device, ...). I could do debug output sometimes with a dos script that writes the debug buffer to HD after a WAIT 30 sec or something. So you can start the script, start WW7, open your printer window and wait until the script has written to disk. This doesn't help of course if the WHOLE machine is stuck...

_________________
X1000|II/G4|440ep|2000/060|2000/040|1000

@broadblues


Quote:

Can you post your wordthworth prefs file?

Aha. That seems to be the problem. I did load a prefs file created years ago when I first had OS4, It was from 2004. Now when I loaded that file, everything worked

The day to day settings are all wrong but at least it gives me something to go on and I think I can now easily create a prefs setting that works - unlike my default one.

Thanks for that suggestion it seems to be getting me somewhere :o)

Not that it really matters but the puzzle is why the prefs I was using worked on previous OS installs but not this one ? At least it can be fixed now.

[Edit]
I just noticed that the old prefs I tried that work, WW7 runs on the Workbench screen, it is something to do with using its own screen that is causing the crash.

Maybe time to look at my Screens Prefs settings. However, WW7 is using the Default which works fine with other apps including other Digita apps like Money Matters and TurboCalc.

Last edited by BillE on 05-Feb-2010 at 10:58 PM.

@BillE

Do you have compositing enabled on your custom screens?

Here I only run Workbench with fancy effects; I defined a own GUI Prefs - based on my default Workbench screen - with compositing disabled and use this for ALL my non-WB screens.

_________________
X1000|II/G4|440ep|2000/060|2000/040|1000

@BillE

Quote:

BillE wrote: Maybe time to look at my Screens Prefs settings. However, WW7 is using the Default which works fine with other apps including other Digita apps like Money Matters and TurboCalc.

hi m8 , TurboCalc does work here (along with Wordworth) so you might be in luck there too :)
As for Money Matters , i am not sure as i never got that one.

Happy that you solved your WW7 issue.

_________________
See my blog and collection website! . https://www.blog.amigaguru.com

@Toaks

Quote:

hi m8 , TurboCalc does work here (along with Wordworth) so you might be in luck there too :)As for Money Matters , i am not sure as i never got that one.

As I mentioned they *do* all work fine

And Organiser, though for some reason the icon colours are never right on that one, but it works.

Quote:

Happy that you solved your WW7 issue

I got WW7 behaving properly this morning. The screen it ran on nor the Prefs made any difference as I still got the crash when running on Workbench, yet the old prefs file still worked on a custom screen.

So I am now using the old prefs file, just updated a bit to get it the way I want and WW7 works with no crashing. It even looks a bit better too as it is now using LikeWB for its custom screen.

@BillE

Did you try re-creating your prefs file form within wordworth on update1, or did you try your OS4.1 prefs file?

_________________
Peter Swallow.
A1XEG3-800 [IBM 750FX PowerPC], running OS4.1FE, using ac97 onboard sound.

"There are 10 types of people in the world: those who understand binary, and those who don't."

@Swoop

The original which crashed was from before update1. I think at first I did have some problems with fonts on WW when first installing OS4.1 update so must have done something then.

I now use one from 2004, which I have now modified again using update 1 OS, and that works well.

I still have no idea what was wrong with the more upto date one but I have replaced it. If anyone really wants to make WW7 crash on opening the Postcript settings window I can send them a copy of WordworthPrefs_duff