Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: spudmiga on January 02, 2021, 09:13:06 PM
-
Greetings,
Up until recently Wordworth has been my goto wordprocessor on the Amiga, I started off on version 4SE then went to version 5 which has been running nicely until I recently had to do a system re-install to a new CF card due to it not getting on with my new 4way buffered interface, got 3.1.4.1 installed with no problems however now when I try to re-install Wordworth 5 it gives me an error 'not enough disk space on Work: you need at least 3 MB of free space" - however the partition is 2 GB!!
I tried installing it to the Workbench: partition which is the same size and it installs ???
But when I go to run, it goes black screen and gives me the software failure error.
I do have FinalWriter 4 here but I am not so keen, and have many files saved in Wordworth format so would like to get Wordworth working if possible. It mystifies me how it no longer wants to work!
Could it be an issue with the way I have set up the Work: partition?
Anything I can resolve in HD Toolbox or something?
My system is: A1200, OS 3.1.4.1, 4Gb CF (2x 2gb partitions), ACA 1221/64Mb
Any ideas appreciated
Spud :(
-
Try installing it as 'expert' and keep the installation protocol as well.
-
There are two issues here: the installation and the crash.
The first problem, the installation complaining about not enough free space, is because the version of Installer on the Wordworth disk is too old. It can't properly detect the amount of free space above a certain amount, so the number overflows and wraps around to a negative number. It can be overcome by changing the default tool on the install icon to a newer version of Installer (at least v43, see Aminet). Either point it to a newer version on your hard drive or replace the Installer on the Wordworth disk (a copy of the disk, of course). The other options are to install to a smaller partition, as you did, or to fill up a partition to the point where there's less free space.
The second problem, the crash, will be trickier to diagnose. As TribbleSmasher suggests, always install in Expert mode so you can see exactly what the installer is doing. Not all install scripts respect this, however, and will copy/replace files without your intervention. I seem to recall that the Wordworth install script does just that, and replaces a number of system files with versions from OS2.1 or 3.0. Conflict between those old files and the newer OS could be causing the crash. Examine the Wordworth disk(s) to see what system files are on it, then check your SYS: partition to see if those files got copied there. If they did, replace them with the newer versions from the 3.1.4(.1) disks.
Also, use SnoopDos to monitor what files are being called. Then you should be able to see exactly at which point the system is crashing (and which file is responsible).
One other thing, make sure you're not hitting the infamous MaxTransfer problem. I think that was finally solved in 3.1.4, but I'm not certain. Check the MaxTransfer setting in HDToolbox to be sure.
-
Of course WW5 is quite old. If you manage to get the WW7 disks, upgrade.
-
The first problem, the installation complaining about not enough free space, is because the version of Installer on the Wordworth disk is too old. It can't properly detect the amount of free space above a certain amount, so the number overflows and wraps around to a negative number. It can be overcome by changing the default tool on the install icon to a newer version of Installer (at least v43, see Aminet).
Hi Matt thank you for the reply.
I would have thought the installer on my 3.1.4.1 system would be newer than the 1996 version on Aminet, no?
I have copied the 1st install disk as suggested and copied the installer from my 3.1.4.1 onto it and this gets around the installation problem so half way there!
I seem to recall that the Wordworth install script does just that, and replaces a number of system files with versions from OS2.1 or 3.0. Conflict between those old files and the newer OS could be causing the crash. Examine the Wordworth disk(s) to see what system files are on it, then check your SYS: partition to see if those files got copied there. If they did, replace them with the newer versions from the 3.1.4(.1) disks.
Also, use SnoopDos to monitor what files are being called. Then you should be able to see exactly at which point the system is crashing (and which file is responsible).
Ok so after running SnoopDOS it seems to crash after loading retina.library
One other thing, make sure you're not hitting the infamous MaxTransfer problem. I think that was finally solved in 3.1.4, but I'm not certain. Check the MaxTransfer setting in HDToolbox to be sure.
Can you remind me where I find this again, I have opened HDToolbox and can only see options to repartition or verify the drive and I don't want to accidentally destroy my partition
Thanks again,
Spud :-\
-
Of course WW5 is quite old. If you manage to get the WW7 disks, upgrade.
Have you tried searching for these? They are nigh on impossible to find legitimately.
Having said that, I did source a cracked copy (yuck) and tried this out for testing purposes and had the same installation problem.
-
Hi Matt thank you for the reply.
I would have thought the installer on my 3.1.4.1 system would be newer than the 1996 version on Aminet, no?
I have copied the 1st install disk as suggested and pointed the default tool to Workbench:System/Installer but I get an error "Unable to compile script. ERROR: Symbol name not valid here on line 1".
Yes, the version of Installer from 3.1.4.1 will definitely be newer. It seems to be too new, apparently, such that it can't parse the old Wordworth script. (This probably means that the Wordworth script is badly written and the newer Installer has more strict error trapping.) Try v43. If that also fails you'll have to go with the fill-up-partition-first route or try installing manually.
Can you remind me where I find this again, I have opened HDToolbox and can only see options to repartition or verify the drive and I don't want to accidentally destroy my partition
Thanks again,
Spud :-\
HDToolbox->Partition Drive->Advanced Options->Change Filesystem. I don't recall what the correct settings for MaxTransfer are, but if you prepped the drive with 3.1.4 I think the defaults will be okay (maybe?). The 3.1.4 docs might have the correct settings listed... can't recall. But it should be easy to find with a search engine.
-
Hi Matt
Since the last reply I have got around the installer problem by copying my 3.1.4.1 installer to a backup floppy, this seems to have done the trick and allowed me to install to Work:
I have set the Maxtransfer to the recommended However I am still getting the crashes, if I set 0x1FE00 recommended setting
If I try it Picasso=FALSE it freezes, if I set Picasso=TRUE it gets to the main screen then black screen/software failure
SnoopDOS says it loads retina.library just before the crash, I am not sure what this does - it seems to be one of Wordworth's own libs as it is not in my system libs drawer.
:o
-
2 things:
I'm looking at my own WW5 disks now and realize why changing the default tool of the install icon failed. For some reason Digita decided not to invoke the installer directly. The install icon actually runs a shell script that invokes the installer. So copying the 3.1.4.1 Installer to the disk was the right move.
You might consider installing again now that your MaxTransfer is fixed, but I suspect now that it's very, very unlikely to have been the problem.
retina.library, I believe, is part of the ancient pre-P96, pre-CGX software for the Retina RTG board. My guess is that WW is trying to open it because of the PICASSO tooltype. I would have thought that setting it to PICASSO=False would have prevented WW from trying to load it, but perhaps not. Try commenting it out entirely (enclose it in parentheses) and see what happens.
Make sure to check your system files (particularly Libs: ) to make sure the versions from 3.1.4.1 are still there.
Can you post your SnoopDos output? Mount RAD: and direct the output to a file there to preserve it after the crash.
-
Hi Matt,
Well I checked the libraries all seemed in order except for a 1996 version of nonvolatile.library so I replaced with the 2018 os 3.1.4 version from disk
Tried Wordworth it crashed again so I restarted, mounted RAD: and set SnoopDOS to log to RAM_0: and attempt to load the program
It crashes as expected but upon reboot it comes up with an AmigaDOS screen that does not recognise any commands. So I powered off for 30 seconds to get back into the system obviously RAD is gone now... I have tried saving a log to my HD partition but it does not seem to save. It sure is mysterious....
Even more mysterious is since doing this... it has inexplicably started working!?!?!?!
Spud
-
After the reboot you need to use the early boot menu to select your normal boot drive as the rad: normally has a higher priority. Or make rad: nonbootable. Without any contents beside the logfile it is useless of course.
-
Well I thought I had it fixed, it began to work. Switch machine off, power on, it still works.
I come back to my machine 2 hours later and try.. it crashes again. The SnoopDOS log file is empty but I did manage to capture this with my camera before it crashed.
Not sure if it helps shed any light on the issue?
(https://hosting.photobucket.com/images/y40/mikepowell2005/snoopdos.jpg?width=1920&height=1080&fit=bounds)
-
I have tried installing again after 'fixing' the maxtransfer problem and this time told the installer to put thewordworth5 libs into their own directory.
One interesting message that appeared when doing this was I am using an old version of post.library ?? I am not sure what this does.. anyhoo, I installed it the newer version as recommended (its going to a separate directory from my system libs anyway) and I got to the beginning of the program, got some strange graphics distortion and the system reset into a software failure as is the norm!!
I may have to start thinking about another word processor sadly, I really do not want the hassle of re-installing my entire system when there is a very real chance this will not solve the issue...
Spud :(
-
post.library is related to PostScript. WW might use it for PostScript/Type1 font support, or maybe PostScript printer or print-to-file support.
Can you try again to share the SnoopDos output? Even if you can't get the log file, expand the SnoopDos window to maximum size before launching WW/taking a photo. If you can get a grab of the icon tooltypes as well, that might be helpful.
And speaking of logs, do you have the install_log_file from the installation?
WW is generally pretty stable. I'm confident you'll be able to get it working, if not v5 then maybe v6 or v7.
-
I am wondering would using Native.lha from Aminet have anything to do with this, I use this in replacement of FBlit as per Hyperion's recommendations for using OS 3.1.4
This is all I could capture full screen before crash, the trouble is Wordworth pops up in front of SnoopDOS so I am having to click back on SnoopDOS before it crashes.. once again empty log file
(https://hosting.photobucket.com/images/y40/mikepowell2005/snoopdos2.jpg)
-
I just did a test install of WW5 on a clean 3.1.4.1 installation under UAE - no problems, and it's a much "cleaner" install than I remembered. Meaning it put a lot less junk on SYS: than I thought it would, and I don't think it replaced any system files. Sorry for the misinformation about that!
So it looks likely that some other element of your system is conflicting with WW. What screenmode are you using for your Workbench screen? What other utilities do you have in WBStartup or user-startup? I gave the Native P96 tool a try under UAE and it didn't seem to cause any problems, so it's probably something else that's responsible.
Please also post the tooltypes you have on the WW icon.
Also, FYI, I'm attaching a SnoopDos log of WW successfully starting on my 3.1.4.1 UAE test system.
-
The screenmode of my Workbench is DBLPAL High Res No Flicker at 128 colours - using Native.lha / Picasso 96 tool this leaves me about 1.6Mb chip RAM on startup on normal AGA.
I have MUI 3.8 installed and BestWB.
WBStartup - AssignWedge, WBDock, ClickToFront, NoClick, FullPOallette.starter & TitleShadow.starter, BenchTrash
Wordworth settings below:
(https://hosting.photobucket.com/images/y40/mikepowell2005/wwsettings.png)
User Startup:
;BEGIN Picasso96
Assign Picasso96: "Work:Picasso96"
;END Picasso96
;BEGIN ADPro & MorphPlus
Assign ADPRO: "Work:ADPro"
Assign ADP_FRED: "Work:ADPro"
Assign ADPROSCRIPTS: "Work:ADPro/Commands2"
Assign FREDSCRIPTS: "Work:ADPro/FREDScripts"
;END ADPro & MorphPlus
;BEGIN Personal Paint
Assign >NIL: PPaint: Work:PPaint
;END Personal Paint
;BEGIN DeluxePaintV
Assign DPaintV: "Work:DPaintV" defer
;END DeluxePaintV
;BEGIN Photogenics-SE
assign pgsse: "WORK:Photogenics-SE"
;END Photogenics-SE
;BEGIN MUI
if exists "Workbench:MUI"
assign MUI: "Workbench:MUI"
if exists MUI:Libs
assign add LIBS: MUI:Libs
endif
if exists MUI:Locale
assign add LOCALE: MUI:Locale
endif
version >nil: exec.library 39
if not warn
if exists MUI:Docs
if exists HELP:dummy ; do not remove
endif ; this entry!
assign add HELP: MUI:Docs
endif
endif
endif
;END MUI
;BEGIN ActivateCrossIDEfix
ActivateCrossIDEfix ALL
;END ActivateCrossIDEfix
;BEGIN CacheCDFS
;END CacheCDFS
Spud 8)
-
Well, the standard troubleshooting routine is to disable those things one at a time and see if it makes a difference. FullPalette, TitleShadow, and ActivateCrossIDEfix jump out as possible culprits. Are you running a regular desktop 1200 with a single hard drive? I'm wondering if ActivateCrossIDEfix is even necessary.
Tooltypes look okay.
-
You are not going to believe this but I tried de-activating each of those and it is still crashing the same way.
I have even disabled Picasso96 and it still crashing, I am completely at a loss now - it cant be the partition being over a gig as it does the same on my 995Mb Workbench partition...
I have installed FinalWriter 97...
When I get chance I can always install WW5 to floppy and access my old files and convert them to another format...
Spud :-\
-
Have just removed Native from the system and viola... Wordworth is working fine! So much for it offering a more stable system...
Works fine if I go back to FBlit however my chip RAM is down to 1.2megs in the same screenmode which isn't very good, certainly not worth the handicap just to run one application.. so I will convert my files from WW to another format then go back to using Native with FinalWriter97 for the time being. I might give AmigaWriter a go once I get a faster setup.
Spud 8)
-
Strange... glad you got it working, though.
Are you using intuition.library v45? In my UAE test system I'm still using intuition v40, and I was also emulating an A2000 instead of an A1200. I wonder if those variables in combination with Native were responsible?
-
I hope this isn’t classed as hijacking a thread. But I logged in this morning, quite literally with the intention of starting a thread with the same title as this one.
System
Amiga 500+
TF536
1Mb chip ram expansion with RTC clock (Amigakit)
8GB HD
WB 3.1.4.1
The issue:
Wordworth 6 & 7
Drawing shapes function
I feel bad for the OP, as I have not had an issue running the word processor, my issue only crops up when I try to use a particular feature.
Over Christmas I was trying to make some Christmas present tags, I thought it would be an easy job. Draw a box, insert a field for FROM & TO. However I soon discovered I had one massive issue. Once I had drawn a box, I doubled clicked to bring up the properties. As soon as I click to change the colour, the screen locks up.
Additional info
Having made an image of my HD, I replicated my system in WinUAE and this freeze up also happens on an emulated setup.
-
Strange... glad you got it working, though.
Are you using intuition.library v45? In my UAE test system I'm still using intuition v40, and I was also emulating an A2000 instead of an A1200. I wonder if those variables in combination with Native were responsible?
Quite possibly, I am using version 45.
It did work but I am going to back to Native/FinalWriter, it gives me more available memory on the system.
I have a copy of AmigaWriter 2.2 here but minimum requirements are an 030 so I will have to wait until the Vampire arrives...
Spud 8)
-
Is thiere a functionality reason for having P96 on a real Amiga that doesn't have 24 bit graphics?
Yes, I am weird. It looks nice, but I never figured out a real reason why people who don't need it, have it.
Emulated Amigas, yes. That I can understand.