Quote:
Could be, however now that it works fine it does so with the same fonts he didn't like earlier (so the question is, why it didn't like them earlier on and it likes them now?).

I don't know, but to me it has to do with First time with all set or not. What I mean is that if at the moment you run the prograsm for the first time you already have all your stuff in place it builds the cache and all goes fine, however, if you add fonts with type manager "After" it has already built a cache, it misbehaves (just my guess).

I added the OWB "Launcher" icon to my dock, and if I recall correctly the > was needed for the standard OWB icon (otherwise an error message pops up).
With the launcher icon this doesn't happen, and both the first time I installed the browser and the last time (a few hours ago) everything went fine because I never added fonts after installation/first launch (I have no problems at the moment, I click the icon on the dock, MUI OWB starts lighting fast, no Font parsing after the first one ever again).

The problem happened when I kept adding fonts with TypeManager after the first launch/parsing, as in subsequent launches it would perform the parsing every time I launched the browser. it seemed the correct thing to do when there were new fonts, but the problem was it kept on doing it even when I stopped adding fonts.

It was on a JFX4 partition, so I guess no problems there. I say "was" because due to other reasons I cancelled that folder, and re-downloaded the file from OS4 depot (in another JFX4 partition).
Since now all the fonts are already installed (I still performed the Font_Download script berore launching it the first time though) and it was a first launch it parsed them all once, and now it starts fine (problem gone).
But I wonder wether or not, installing new fonts in the future might cause troubles again...

Hi Guys,

I have the following problem:

I first installed this browser on my Update 3 "first attempt" (ie: installation of Update3 on top of my previous/used Update2 installation) and everything was fine: I installed the additional fonts with the provided script (by the way, the mos icons were used and all I had to do was double clicking the icon) and since I already had Code2000 in my fonts drawer it was parsed along with the other at first boot.
As advertised it does so only the first time, subsequent launches were fast.

Due to other problems I performed a tidy clean reinstall from scratch of the OS (Update1 from the ISO CD, then Update 2 and then 3) transfered on the system (from a back up CD) the MUI OWB LHA, unpacked it and I immediately noticed something strange:the mos icons were gone and I had to launch the download fonts script from shell (probably I'm missing some PNG icon handler I previously had).
The Browser launched and parsed the fonts but I forgot I had no Code2000 installed yet. Since I had Bitstream Cyberbit too, I used this first (installed with typemanager of course) closed the browser and at boot it re-parsed the fonts again.

I said to myself, "well I just added a new one, good". I tested some japanese websites, but the font was a little to light so I decided to install Code2000 as well. I closed the browser and also installed code2000 with type manager. When I re-launched MUI-OWB it re-parsed the fonts, and I said to myself: "well I just added a new one, good".

However it does so all the times now, I even tryed the FixFonts utility (hoping it would fix the database or something) but in any case, every time I launch MUI OWB the font parsing happens again and it takes a lot of time (very annoying).
Does anyone know how to get rid of it?

Nice read, I remember back in the day when there were talks about Transputer based accelerator cards (for 3D) to be eventually available for the Amiga, now we have an entire Xmos subsystem built in the next machine. Must have been destiny

Quote:
Really?

Anyway, Happy Birthday to all Amiga makers born that day! :)

I'll cut and paste part of my guide that talk about this subject:

Open the screen-modes utility and click on the second tab (the one that says "Monitors"):


To disable DCC untick the "Detect settings automatically".
In order to get low res modes to work specify larger scan-ranges you can do this below on the right, where it says Refresh Rates (also just above the "Save Monitor" button) place your cursor in the scan ranges text boxes, and specify the following ample ranges (just to make sure):

Minimum VSync: 50 (that's 50hz)
Minimum HSync: 28000 (That's 28Khz)

Maximum Vsync: 160
Maximum HSync: 96000

Modern CRT monitors won't go bust if you try frequencies they don't support, they will automatically go in "stand-by" mode instead (with some others displaying a warning message such as "Out of Scan-range") so don't worry. With these ample ranges you will make sure that the new resolutions will be accepted and added to the "Radeon Monitor" resolutions list.
NOTE that all my screen modes have a tick beside them, if yours don't (after you deactivate "detect settings automatically") tick them all! Otherwise when you re-boot workbench won't find any active mode (it happened to a guy once).

Now press the add resolution button and create a 320x256@60 screen mode (this will be a double scanned screen mode that should be easily usable on a LCD) click on "Save Monitor" button and close the window, you will be informed that the new changes will be available only at the next (re)boot, and asked if you want to re-boot now.
Re-Boot. After you get back to WB go to the resolution list to see if the new res was added and test it.

P.S
This won't solve the lack of DMA in the sound driver but at least the low res screen mode will be as big as it gets.
As usual for perfect look and scrolling smoothness I suggest anyone to grab a cheap CRT monitor and connect it to the second video out of the graphic card (using a picasso96 non-doublescanned screen mode). This way the games will look "native A500" and perform in the absolute best possible way.

Definitively a mix of hi-res (E-UAE running at 640x480) + alpha sound drivers (no DMA) is causing the audio problems in Lotus 2.
On my Sam Flex running at 800Mhz + native screen mode (picasso96 320x256@150Hz) the music during the intro and loading sequence play just as good as on my A2000 sitting right below it.

I'm sure that when the final DMA drivers will be ready (and when used with a native mode) also R-Type 2 should be fine on the 460EX.

@MickJT

SDL version is way slower in fact, but there are games which are not demanding and will work fine with both SDL and AmiGFX (like the first turrican for example).
Using this same game with both version I get the perfecttly smooth scrolling (with no screen tearing either) under SDL, (same with other non-demanding games) while AmiGFX never reach such perfect results under any condition (it gets very good, but never perfect).
My guess is that when using the SDL version on a powerful HW the list of perfectly working games should grow exponentially with the system power, thus a Sam440EP might only play Turrican 1 smooth (and a few more), a Flex800Mhz will add a few titles to the list, a Sam460EX even more, and hopefully the x1000 will nail them all.
Granted I'm always talking about using a native 150hz 320x256 mode (non-doublescanned) on a CRT, if we talk LCD, there is no way to get such perfect results with any of the current versions.

@MickJT
Advantage of SDL port: as you remember you sent me your SDL recompile a while back (the one that is dynamically linked)and one thing I noticed is that it reproduces the smoothest possible scrolling of any other version.
I'm quite an expert when it comes to set emulators to mimic the original machines 1:1 (I did this on PC way before coming back to Amiga) I work with both advanced video options and emulator settings, and as everybody probably knows I'm not afraid to try all these settings on several different monitors (both LCD and CRT monitors and TVs).

Using AmiGFX (which returns correct audio without hiccups) there was no way whatsoever to get 100% rid of scrolling stuttering and screen tearing (I've tried everything).
The best I managed to get is "very sporadic" V-Sync problems coupled with very very sporadic micro-stuttering (all this only if coupled with a CRT and a native 320x256@150Hz screen mode) which is very good, however the SDL version you sent me goes one step ahead and it's just perfect.

Using the same screen set-up described above, going around in a multi directional scrolling game like Turrican for example (or any other for that matter) NEVER produce errors in scrolling smoothness or screen tearing, the screen scrolls at a constant silky smooth rate and stays always in one piece (no tearings ever under any condition).
Sadly sound reproduction is good only in 50% of the games on a SamFlex, hopefully better hardware will solve the problem.

+1 :)

@Snuffy
If your XE is working just fine, then no need for a Sam right now.
However, later on, when the new 3D subsystem will be delivered, the XE will be hampered by a slow bus and poor choices when it comes to GFX cards.
For example, antique here is using a RadeonHD 4890 with his 460EX, try that with your XE
Of course as I already said, for now it's just food for "later thoughts" :)

@kas1e
I see what you're doing, you're pestering Hans so that he spills some beans...
However don't doubt his word when talking graphic programming as he is quite The expert.
I know how you feel, you want to know "when", "how", details and so on, and patience is at a premium these days...
And besides, amigans are a very tough crowd :)

Quote:
Indeed Sam440 might be more picky than other systems when it comes to GFX cards, I hope that A-cube and dealers such as Amigakit will provide "certified" cards when the time comes...

I'm sure Hans will explain things in detail as soon as he sees this, for the time being what I reckon is that since we only have 2D drivers for RadeonHD cards, Sam440 owners (Flex owners in particular as it's the only 440 model to feature a 66Mhz PCI bus) should look for PCI versions of RadeonHD cards.
In particular I saw the HD2400 and HD4350 in PCI version. Support for recognizing the first was added in a past U-Boot update I don't know if the 4350 is also recognized at the moment.

This card should be ideal (supports Shader Model 4.1 although I don't think it's relevant for us, with Gallium we should get access to GLSL 1.20 however):

http://www.hisdigital.com/un/product2-444.shtml

I vote for this:

http://www.koffice.org/

:)

Yeah no wonder who wouldn't? (be confused I mean)

But these guys are shady at best, IMHO they are just interested in stealing an idea or two, and stop something that could steal their thunder in case it ends up being produced together with a commercial partner of sorts.

If you ask me the last time I checked a keyboard (all in one) Amiga it was using AmigaOS, so that's where these cases belong

@Loriano
As ChrisH said, DON'T send them NOR show them cad design's.

reminds me of the usual discussions about programming IDEs a while back:

User n.1: we need something like visual studio!

User n.2: No! Visual studio is for lamers! The real pro use a crude text editor!



Give us Thunderbird I say, then anyone who doesn't like it, is free to use anything they like ;)

@kas1e
Wow, we now have both UltimaVIII and Baldurs Gate 2, who would have thought a while back! Thanks for the great job! :)