@joerg

except for 2 also incomplete directories the dir command from shell doesnt show any other, only the icon files for the missing ones. i can also enter these present dirs via workbench. i had not realised it before.

@joerg

sorry to say, even partition magic under os4 with sfs partition as a target had the same effect. some 1.3 gig data are being recovered, of which only that in the root directory are accessible. various attempts of using protect command to unlock the directories didnt succeed. may it be the directory tree is damaged beyond repair but 1.3gb of what data are sfssalv and partition magic recovering then, since they spit only a few warnings underway and continiue to what seems to be some succesful end?

@ChrisH

the situation is not that critical. i should have the most of the data backed up somewhwere. however i would like to be able to recover the partition using appropriate tool, that seems to contain bugs alas. i will try to contact joerg via mail, lets see what he sez.)

@jahc:
no, since the system assumes only the files in the root are present protect with whatsoever arguments also applies only to them. sigh.

i just discovered today that one of my partitions disappeared from the desktop. it is seen as unformated maybe due to rdb failure. the data system can be completely detected by sfssalv as far as i was able to judge it. but after running recovery onto another clean partition the directories cannot be opened anymore. in oposit to data in root that are accessible without problem. the space used by the data on this new partition seems to indicate that in fact everything has been recovered. it is alltogether about 1.3gb. i wonder if there is some bug in the program really, it seems it is put together a little carelessly at least what concerns gui.

@nubechecorre

the 68k voodoo and w3d drivers too? what about the elbox radeon driver? where does this come from?

warp3d for the radeons would be something that could justify gfx hw update, but i do not think anyone bothers. as i asked elbox about that some weeks ago, they said to their knowledge there is nothing in the makes. which means the w3d drivers for the woodoo are not done by them. so who is maintaining this system if anyone?

@joerg


[Quote]
@wawa
Quote:
also i tried the 1.4 version for 68k. does it mean that you are going to continue this development?
No.
[/Quote]
that hurts.. oughh. auch if its probaby most reasonable. but why did you do an update in this case?

[Quote]
Quote:
are you aware that soeone seems to have made extensions to 68k ixemul libraries, now version 48.3 that you can find on this site: http://megacz.back2roots.org

The other updated libraries there (xml2, pthreads, freetype, ...) would have been much more important for an usable AmigaOS 3.9/m68k OWB port, but I didn't know anything about this page.
[/Quote]

at least now you know the site.

at joerg: also i tried the 1.4 version for 68k. does it mean that you are going to continue this development?

are you aware that soeone seems to have made extensions to 68k ixemul libraries, now version 48.3 that you can find on this site: http://megacz.back2roots.org

i do not know why he didnt post it to aminet neither can i judge the quality of improvements, but i downloaded it, installed the appropriate versions and they are working with your current 68k owb port.

@joerg: it is working better now it seems, but the bug that hangs the system when you interact with owb while its loading a page is still making apperarance now and then. like when you input something into the adress bar or klick on an already rendered link.

@joerg

Quote:
i suppose so. afterwards i had once a hangup after i just clicked into the window while it was loading amigans page. unfortunatelly i use elbox drivers since i need the access to pci tv and network card. i see, now and then these drivers fail but mostly the problems are not critical.

all in all i think the problem is the same the other people had on classic.

@jorg
i have experienced a system hangup when (slowly) dragging vertical scrollbar several times. i wasnt able to observe more closely what leads to the crash. my system is basically a4k with csppc, mediator and voodoo if that is of any importance. other than that there is great improvement in speed, function and stability, the owb is becomming usable as first choice browser on os4 the way i see it. only that memory thirst worries me somehow. wouldnt that make sense to implement some kind of privately managed page file like clarissa or photoshop are using?

?h: havnt read the thread closely. i think my prob is the same as voodoo and k-l have reported

@joerg
first of all i admire your effort and wouldnt want this to appear as any kind of critic. but havig installed both the os4 and the 3.9 on my a4k rig i still prefer the latter. i tried the 1.3 owb version and admittedly it was really slow on the real 060. but would that be to much work to adopt owb to run in wos environment?