@lylehaze

> "There is NO BenchTrash on a fresh install. There is NO BenchTrash on the install CD."
>
> Umm, maybe someone threw it away??

I suggested to do so because its an 68k program which cant work on PPC OS4.
Never tested it but IMHO it has to SetFunction() dos.library to implement a
system global trashcan, and it will of course only patch the 68k jumptable,
not the PPC interface. Nobody disagreed so its now missing. No sources
available so we cant compile a PPC version.

@Chris_Y

i have the same problem !

_________________
Sam 460EX, 2Gb Ram, Radeon R7 250, AmigaOS4.1 FE
A4000 PPC604@233, Mediator
A1200 PPC603@160, Mediator
uA1 G3@800, 512 Mb [sold]

@TetiSoft

I removed both Turboprefs and Turbospool from WB startup and rebooted.
PrinterPrefs showed my "correct" saved settings.
Started Turboprint's "graphics publisher".
My PrinterPrefs in env: reverted to "default" upon startup.

Rebooted.
PrinterPrefs still showing correctly, of course.
Started Turboprint's "print manager" in same directory.
My PrinterPrefs in env: were NOT altered.

?

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@Chris_Y and
SOFISTISOFTWARE

I can print out web pages with Voyager 3.2, so it is NOT a print problem.
It is an outstanding issue with AWeb, imo.
In the meantime you can use Project/save as .iff and load the resulting files
into Turboprint and print from there.

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

Quote:

I don't think Andy (Broadblues) ever claimed print was working as hoped in AWeb APL lite. He is certainly free to correct me on this.

3.5.0.7 prints OK here when I tell it to not print background. I never tried that under update3. This is with Postscript set as the preferences printer, going to a networked Minolta laser.

One of these days I'll have to try it with backgrounds printing. But when I did that under update 3, it would print a strip fine for the left side of the page, and then fill the rest of the page with stripes.

Paul

_________________
Builder of Frankenthousand, the monster A1000
The Young Frankenthousand A1-XE G4
X5000

@tonyw

Quote:

The problem is that C: is the lowest priority in the Path, so any other version of "date" will be found first.

Yes this has been the case, since all the OS4 prelreases? On my OS3.5 install C: is just after ram: I can't remember if I changed that myself or if it came like that.

The first thing I do on updateing my S:Startup-sequence is to put C: back near the head of the path.
It cause problems with OpenUrl and possibly some others.

I use a totally different path for abc-shell, so that unix tools are used in preference to amisos ones.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@Raziel

Quote:

Such problems?

I fear we must use the shell until the next (os4 final ?) update...

When it will be out ?

_________________
-------------------------------
AmigaOS, the last hope...

I must say the update went very well. I was so nervous about updating U-boot that I did not do it when update 3 came out. I got the kids to bed and told the wife I would hopefully see her in the morning. In an hour I had everything running. Of course I spent the next three hours playing and paid the next day. I can't say it enough, "I love this machine and operating system." I especially want to thank Rogue for releasing it when it is done!
There are some problems I am having though. I have searched Amigaworld, but have not found the answers.

-DVPlayer's sound crackles when a movie plays.

-I have two harddrives in my A1-XE 4G. I decided to format one as SmartFileSystem. I followed Toak's tutorial from Intuitionbase, but when I try to quick format the system hangs. Any ideas?

Thank,
John Paul

@number6

Quote:

I don't think Andy (Broadblues) ever claimed print was working as hoped in AWeb APL lite. He is certainly free to correct me on this. System printing -will- print web pages under Voyager 3.2. I have successfully done this under both update#3 and now under update#4.

A quick potted history of AWeb's printing on OS4....

Under OS4 prerelease:

AWebPPC would print but only from 8bit screens. This turned out to be due to an old assumption that only turboprint could print deep screens, so if turboprint was not present prining was disabled for deep screens.
Replaced this with a check for a recent version of printer.device, printing now worked on deep screens.

At this stage I hadn't got turbo rpint to work for me, so printing with turboprint was untested.

updates 1:

still works for all screen depths

update 2:

still works, turboprint comes to life on my setup, and AWeb seems to work okay with it.

update3:

printing on AWeb breaks, whether on deep or 8bit screens.
The left quarter of the print out print as normal but the right 3/4 is garbage.

I haven't been able to determine where the problem lies, AWeb prints by rendering to strips of bitmap which are friends of the screen mode, these are fed to the printer.device in way that always used to work. Study the various docs available have given me no clues as to what may be incorrect.

update4:

just did a quick test,

with turboprint running, AWeb prints noise.
without I got a partial result.

The characters OX appear just before the first block of graphics which are printed at 4 x size (dimension increased by factor of 4) following block print as expected. THis is without backgrounds.

This would suggest some garbage is output to the printer driver just prior to the graphics data.

Above printing was from my 16bit workbench screen.




I strongly suspect the issue for update3: is how printer.device deals with bitmaps, in particular deep bitmaps. AWeb does render to the bitmap correctly, otherwise 1 the screen would be corrupt, 2) save as iff would not work.
this now appears to have been resolved for update4:


Between update2and update3 the endiannes of the screen modes changed, could turboprint be expecting littleendian bitmaps?

Last edited by broadblues on 18-Feb-2006 at 03:05 PM.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@wegster

When I checked the settings for a SiI0680 card I found they had reverted to PIO mode but this was fixed after reseating the card. I'm surprised it didn't give an error of some kind. However I have been experienced a long delay (40 seconds) during bootup after the kickstart modules have been loaded and from the serial log the delay appears just after message' [init_unit] Trying to configure unit 0' appears. This started happening under Update #3 and I can't figure out why - it used to be fine.

As an aside, the UBoot Preferences editing program, while it displays PIO in the pull down menus, it does not let you select it. This applies for all Si prefs.

Garran

I think I found another one. If you play with the gui prefs, and set the menu transparency, the percent transparency isn't respected by ContextMenus - it respects that you did ask for transparency, but it seems to be about 50% regardless of what you set as % transparency.

It's easy to reproduce this: go to the GUI prefs program, then the "menus" tab, then select you want transparency under "Appearance Properties". Then set the transparency to 90%. Click on "Use", then pull down a menu and see how wispy it is. Right-click on something and you'll see that the popup menu is a lot more "solid" than the pulldown menu.

@tonyw

Thanks, I forgot to do that after I installed update 4. OOOps! However, I still get somewhat strange behavior. If I use CDRW and insert a rewritable CD in my drive, I can format it fine with formatCDRW. However, if I use DVD+RW and insert a dvd+rw disk, I cannot format it. I can do a FORMAT DVD+RW or a CONTINUE DVD+RW FORMAT until the format is complete, but I then have a disk with low level formatting but no filesystem. If I try to do a quick format using formatCDRW, the phrase "formatting, please wait..." flashes into the window for a very small fraction of a second (too fast to see clearly) and the formatCDRW program returns to its usual state, waiting for me to select a button. However, the disk is not formatted and continues to show as a ghosted icon labelled "DVD+RW Uninitialized". If I then try to format it with any of the other format tools the format fails. sfsformat reports "not a dos disk", as do the ffs format commands (system/format and also format invoked in the shell). The ffs commands will format the disk if I do not select "QUICK", and the format will be very slow (estimated time, 480 hours) unless I select "NOVERIFY." In that case, the format takes about 45 minutes and ends withe the "not a DOS disk" message.

This slimline matsushita drive is a cdrw/dv+rw/dvd-rw/dvd-ram drive, and it works just fine with cdr, cd-rw, and dvd-ram, but not with dvd+rw (I haven't tested dvd-rw yet), so it doesn't look like a hardware problem. Or if it is, it is a rather confusing one.

Could anyone give me any clues as to what might be wrong?

My system: microA1 g3 800MHz, Travla case with non-travla powersupply, mastushita slimline cd/dvd/dvdram as primary master, WD notebook style 80GB HD as primary slave, and nothing in the pci slot.

Thanks for any help!

--Stuart Anderson

@wegster

Anybody know what powerpc.library does, or what it is supposed to be used for? Does any other software need this library?

Ever since I updated my OS4 to update #3, I have been plagued by crashes of AmigaAMP. Almost everytime I launched AmigaAMP, it would crash. If it did not crash, it would work just fine. If I quit AmigaAMP, it would crash as soon as I launched it for the second time. This behaviour continued after I installed update #4.

This had me completely baffled ... until just a few days ago, when I noticed that powerpc.library always showed up in SnoopDos and Grim Reaper everytime AmigaAMP crashed. Renamed powerpc.library to something else, NO MORE CRASHES. Checked several times just to be sure.


Now that I have a working AmigaAMP, I am concerned that some other program may actually need powerpc.library ....


---
redfox

specs:

MicroA1-C (µA1-C)
IBM PowerPC 750 GX V1.1
CPU speed: 800 MHz
256 MB RAM
40 GB Maxtor hard drive
LiteOn DVD combo drive


--edit to add specs--

Last edited by redfox on 19-Feb-2006 at 04:58 AM.

@redfox

powerpc.library is used for WOS programs.
Deleting -does- stop the crash in AmigaAmp...but I wouldn't recommend that as
a solution.
Try leaving it in libs and changing AmigaAmp Prefs/System/Engine to "WarpUP"

#6

Last edited by number6 on 19-Feb-2006 at 05:02 AM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@redfox

I'm not sure but I think powerpc.library is for some PPC accelerators that are used in 68k Amiga's. Some programs may interpret the presence of that library to indicate that they are running on such a system and attempt to execute some code that doesn't work on a 100% PowerPC system like OS4.

I think we need a list of libraries, devices etc. that should not be used on an A1 with OS4.

_________________
X1000 with 2GB memory & OS4.1FE

@Xenic

WOS.
Another example:FroggerNG A/V player.

The problem in "AmigaAmp" is that the "engine" iirc is set to default "mpega.library".
This default will not work and the equalizer will not function with such a setting
anyway. It needs to be set to "WarpUP".

(and before anyone asks, No you -don't- replace your OS4depot libmad mpega.library
with a WOS mpega library to make this work.)

#6

Last edited by number6 on 19-Feb-2006 at 05:15 AM.
Last edited by number6 on 19-Feb-2006 at 05:13 AM.

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

You were right. I was not able to use the equalizer.

Warning! The equalizer needs AmigaAMP's
PowerPC decoding engine! You can see
the graphics now but moving the sliders
will have no effect on the sound.


Quote:

Try leaving it in libs and changing AmigaAmp Prefs/System/Engine to "WarpUP"

So, I gave this a try and reset the machine .... BINGO ... comes up in WarpUp mode and works fine (after renaming powerpc.library back to normal).

I also noticed, doing a SnoopDos trace, that AmigaAMP no longer searches for ppc.library, 68060.library, 68040.library and powerpc.library.

However, now I get that nice message when I quit AmigaAMP ...

***Command 'AmigaOS4:AmigaAMPv2.16/Engines/External' returned with unfreed signals 80000000!


for the help

redfox

@redfox

Quote:

***Command 'AmigaOS4:AmigaAMPv2.16/Engines/External' returned with unfreed signals 80000000!

That message is *cough* normal.
It is worth it I think in order to use the equalizer.
(we still have a similar message concerning unfreed signals on MPlayer versions,
also on quit)

#6

_________________
This posting, in its entirety, represents solely the perspective of the author.
*Secrecy has served us so well*

@number6

I agree. Works great otherwise.

again

Some problems I am having. I have searched Amigaworld, but have not found the answers.

-DVPlayer's sound crackles when a movie plays.

-I have two harddrives in my A1-XE 4G. I decided to format one as SmartFileSystem. I followed Toak's tutorial from Intuitionbase, but when I try to quick format the system hangs. Any ideas? I have also tried the latest SmartFileSystem uploaded last night.

Thank,
John Paul