"GreenEagle" and I were playing with his machine today and I was showing him that whenever you boot the machine, you can't print through Turboprint unless you call up the TurboPrefs and select "Save". You don't have to change anything, just "Save" it. Turboprint will work fine from then on.
I remember this same problem from back in the OS3.9 days, so it is nothing new. We ran Snoopy and looked for any new files or ENVs after saving the prefs, but found nothing.
Has anyone found a way to make the settings permanent, so that you don't have to open TurboPrefs after each boot and reSave?
Have a look in your Turboprint/Extra drawer and you should have a TURBOstart icon in there. just drag and drop it in WBstartup.
If you have/had previously installed Turboprint to your SYS: partition then drag and drop will actually move the TURBOstart icon, rather than copying it to Wbstartup.
If you have then just copied your Turboprint installation to subsequent updates, you may have lost the TURBOstart icon.
if that is the case, you do not necessarily have to to a re-install, just unarc the Turboprint .lha files manually to ram: to find the TURBOstart tool.
Essentially this just runs Turboprefs, which is in your turboprint drawer. The icon default tool is Turboprint:Turboprefs.
I use NotePad for printing text files. With TurboPrint active, NP refuses to print until I turn TP off. Another thing I found was if I config Printer prefs then config TP, my Printer prefs changes or if I config TP, my Printer prefs changes. In other words the 2 pref settings interact. Because of that,I removed TP from WBStartup & activate it only to print gfx or pdf's.
Look, only one leg, count em, one! X1000/PA6T@1800MHz/2Gb/Radeon 4850
Another thing I found was if I config Printer prefs then config TP, my Printer prefs changes or if I config TP, my Printer prefs changes. In other words the 2 pref settings interact.
TP creates printer.prefs and printergfx.prefs files in OS3.1(!) format, the OS4Final printer prefs editor didnt accept such old settings files anymore, the OS3.5 format was minimum. Changed that, from the releasenotes:
Quote:
Printer 52.3 (30.1.2007) (dwuerkner)
- For backwards compatibility to TurboPrint V7, old OS3.1(!) prefs files created by TurboPrint where the PGFX IFF chunk was stored in a separate file and where the PDEV IFF chunk was missing are accepted for unit 0. This avoids falling back to default prefs after calling NoTurbo.
I've ported all OS4 printer drivers to PPC except PRINTERS:File where I dont have the sourcecode. In the past creating printer drivers for AmigaOS was a third-party-job, I dont think that it makes sense that the OS4 developers waste their time with writing printer drivers (AFAIK there exist lots of printers...) when neither the printer manufacturers nor third-party commercial developers do that.
You should ask for an update of TurboPrint or Studio IMHO, or use PostScript or PCL printers. When your PCL printer has features which are not supported by an OS4 printer driver yet, feel free to modify the public PCL printer driver source code (NDK 3.9, will be updated in the next OS4 SDK) or to search a developer which does it for you.
I've ported all OS4 printer drivers to PPC except PRINTERS:File where I dont have the sourcecode. In the past creating printer drivers for AmigaOS was a third-party-job, I dont think that it makes sense that the OS4 developers waste their time with writing printer drivers (AFAIK there exist lots of printers...) when neither the printer manufacturers nor third-party commercial developers do that.
You should ask for an update of TurboPrint or Studio IMHO, or use PostScript or PCL printers. When your PCL printer has features which are not supported by an OS4 printer driver yet, feel free to modify the public PCL printer driver source code (NDK 3.9, will be updated in the next OS4 SDK) or to search a developer which does it for you.
Going for PCL or PostScript printers is ok for now, but ultimately the current drivers are going to get old and someone's going to have to write new ones. I'm not expecting TurboPrint to be updated. I wish that printer manufacturers would just all use PostScript. Unfortunately PostScript is only available in expensive printers.
Once the new SDK is published I'll probably have a go at writing a driver for the Epson Stylus C8x series because that's what my printer is (well it's a CX6400 multifunction, but the printer mechanism is the same as the C8x series).