OWB 1.12 available

OWB runs much better on my system no GR or yellow banner :)

thanks Joerg for the Quick updates keep em coming its progressing extreamly well

@poweramiga

Yep, and the fonts look great now! GREAT job joerg! When I have some cash again i'll donate some to him for sure.

Seems almost like we need an OWB forum here on amigans ;)

@orgin

Quote:
With updates this fast, there's certainly a lot of OWB threads appearing.


*** edit - This was my first post from OWB
Its getting better all the time. ***

@Swoop

I'm going to have a go - as soon as I've dragged the kids round Mozza's and had me tea !

a contrib could be in order too, come payday !

@poweramiga

Too bad I"m at work now. But all my problems with 1.10 went away once I rebuilt my font directory with typemanager, anyway.

I'll have to try 1.12 tonight if our electricity at home comes back on. (Stupid winter ice storms. . . . )

Paul

Thanks joerg

@Paul

Well often when electricity stops during winter, it because ice has formed on the electric cables, the cables becomes so heavy they fall off, lucky her in Norway its almost as warm as the Norwegian summer thanks to climate change, we don?t experience snow that often anymore.

This is really amazing. When I got all the fonts working probably this update impressed me alot! It looks better and it feels faster.

Joerg, I can't salute enough. I can make a donation, however, and I'll do this tomorrow!

Wow, that's fast!
After installing all the fonts here, (cyberbit an corefonts) the whole text is displayed. However, here on amigans I can't click the threads links (on the main page for example).

gone to define default other than Bitstream Cyberbit font, maybe some "Sans" one.

Great job!
Jack

@joerg

Well, i did eveything you said was needed for 1.10/1.11.

I attached all the font families to the single fonts (which
was a helluva lot of work), i restarted, but even now, under
1.12, OWB keeps crashing on the first start.

You know the source, could you just take a peek onto the
stack trace part and see WHAT is causing OWB to crash, so i
might have a look at my system to see whats going wrong on
MY end as obviously everyone else enjoys the browser... :-/

Thank you

Symbol info:
Instruction pointer 0x7BF2D248 belongs to module "" (HUNK/Kickstart)

Stack trace:

native kernel module newlib.library.kmod+0x00000b50
native kernel module newlib.library.kmod+0x00000dc8
native kernel module newlib.library.kmod+0x00002380
native kernel module newlib.library.kmod+0x000028e0
OWB:_start()+0x180 (section 1 @ 0x180)
native kernel module kernel+0x00035be0
native kernel module kernel+0x00035c60


PPC disassembly:
7bf2d240: 66dc39e6 rldicl r18,r31,26,18
7bf2d244: 66dc39e6 rldcr r18,r31,r26,18
*7bf2d248: 66d3538c .word 0x7BF2D248
7bf2d24c: 66d3538f .word 0x7BF2D24C
7bf2d250: 66d353c2 .word 0x7BF2D250

System information:

CPU
Model: Motorola MPC 7447/7457 Apollo V1.2
CPU speed: 1266 MHz
FSB speed: 133 MHz
Extensions: performancemonitor altivec

Machine
Machine name: AmigaOne
Memory: 524288 KB
Extensions: bus.pci bus.agp

@Raziel

Hi,

Yep, I still have the same trouble as you on startup.

The frustraiting thing is that it is th ONLY program that I use that crashes in startup.

Ciao,
Trev Daley.

@tldaley

Quote:
I second your emotion.
It's quite discouraging NOT to be able to nail this.

@poweramiga

Wow, I have just got up and running again using the A1 XE I just purchased on Ebay. Boy do I have some catching up to do with all the latest program releases.

I am using the latest OWB and it is great, it has really improved at a frenetic pace. Well done to Jeorg and all concerned.

ace

@acefnq

Good to have you back on board with an A1 XE :)

@tldaley

Quote:Do you have a 7457 CPU module from ACube as well?

@Paul

Quote:

What exactly is Typemanager supposed to do? I never really understood its purpose as copying fonts to the sys:fonts drawer always worked fine for me.

Hans

@joerg

Quote:

Given his .sig on the AmigaOS4 ml, he has not

Quote:

But is a G4 ... why, do you smell something?

@Hans

Quote:Typemanager "installs" Fonts on to AmigaOS. i.e. it creates the .font and .otag files in your selected font directory.
E.G. using Cyberbit.zip as an example.
1. Unpack Cyberbit.zip to ram using unarc.
2. launch SYS:System/typemanager
3. Select ram: as your source directory, and cyberbit.ttf is displayed in the left hand window.
4. Select cyberbit.ttf.
5. Select your destination directory, usually sys:fonts
6. Make sure that "copy files during installation" is ticked (the default), and select install.

Typemanager then copies cyberbit.ttf to the _TrueType directory in your selected font destination folder, and also creates cyberbit.font, and cyberbit.otag also in your selected font destination folder. AmigaOS programs can now find them and use them.

Pagestream uses the font data files directly, and Wordworth installs it's own .font and .otag files in WwFonts/UFST, so neither of these programs use the system .font and .otag files.

@joerg

Quote:

Hi,

No mine is an original Eyetech A1XE with G4, I?ve had it soo long I can?t remember when I got it.

One of the first boards I think, even has the sound chip onboard.

Ciao,
Trev Daley.

PS. I see I need to update my sig here.

@Jack

and at all that have problems with not working links. I had the same problem and solvet it by running typemanager, deleting all the installed fonts in the right column (don't be afrait, it won't delete the actual fonts, only their installation), then re-selecting on the left fonts: as source and re-installing all the fonts (don't forget to re-install also fonts you installed from other sources, if you want to get them back in your system)

Luca