@Chris

Not able to install netsurf 2.0, I have tried to install this one and I have a DSI error during loading, with the normal or the cairo version:

Crash log for task "NetSurf"
Generated by GrimReaper 52.7
Crash occured in module libxml2-2.6.so at address 0x6F6A2DD0
Type of crash: DSI (Data Storage Interrupt) exception

Symbol info:
Instruction pointer 0x6F6A2DD0 belongs to module "libxml2-2.6.so" (HUNK/Kickstart)

Stack trace:
module WORKBENCH:SObjs/libxml2-2.6.so at 0x6F6A2DD0 (section 0 @ 0x3DD4)
module NetSurf at 0x6F978AF8 (section 12 @ 0x43AD8)
module NetSurf at 0x6F978DBC (section 12 @ 0x43D9C)
native kernel module newlib.library.kmod+0x00001f38
native kernel module newlib.library.kmod+0x00002bcc
native kernel module newlib.library.kmod+0x00002d48
NetSurf:_start()+0x170 (section 8 @ 0x170)
native kernel module dos.library.kmod+0x0001ea6c
native kernel module kernel+0x00057350
native kernel module kernel+0x000573d0


PPC disassembly:
6f6a2dc8: 3b9c0008 addi r28,r28,8
6f6a2dcc: 419a005c beq- cr6,0x6F6A2E28
*6f6a2dd0: 807c0004 lwz r3,4(r28)
6f6a2dd4: 7f44d378 mr r4,r26
6f6a2dd8: 577f1838 rlwinm r31,r27,3,0,28

Hello,

Thanks a lot for this release

hope you will receive feedback and help for the 'slow' speed on SAM I have read recently on another thread.

Too bad you haven't a real amiga Maybe a bounty could help you to buy a part of it because Mane is verry important on the amiga world.

@joerg

Quote:

Thanks a lot, joerg That will give great help for acessing amiga users modem for setings, for page with login+password for private page (beta software,....).


@kas1e

I'm using the same modem/router for my 2 amigas and all work fine. Just Ibrowse or OWB crash sometime but don't know if caused by OAS4.1 on the SAM.

@ZeroG

The key has been formated as FAT32 with AOS4.1. Take now a verry long time to be initialized by AOS (key led flicker during a long time).

after formating by AOS4:
L:crossdodfilesystem (FAT2)
used: 9.3 go (62%)
free: 5.6 fo (38%)
size: 14.9 go
block:512 octets

A verry strange formated result by OS4. This key work without problems with a PC usually. It's why I have the problem to said It's a faulty Key and must be remplaced because no problems on a PC (key used often at job or on the classic+spider2).

I think I will full this key with the classic+spider2 for checking where came the problem

to be continued....

@ZeroG

Thanks for the keyboard shortcut .

Don't know this point (in fact not seen all about aos4.1 because just 3 months old user).

AOS4 format the key actually. I could make test more often with this keyboard shortcut.

ZeroG:

This problem is known by the aos4 programmers and will be resolved in the next update ???

Do you know something about the problem (informations) ??? Just for me for not beginning mad each time th eproblem came).

@nubechecorre

Yes, I hope also this problem will be resolved soon... but I can't explain actually what happened (FAT32, long file name or strange file name,...)

@all

Hum. same thing (same key, same FAT32 filesystem,.......) and same problem.

this time, just copy with filer a file on SYS: called:
Crashlog_Project1-08mai2009-2.exe_2009-05-09_09-05-20.txt (20ko of crashlog .txt).

on the FAT32 key, formated with a PC some days ago and filled with maybe 100mo datas on differents drawers, from a PC.



8+3 Drawers and files have been created with the content of the 20 ko crashlog. It's not caused by the filemanager.

1. Maybe the cause is a file with xxxxxxxxxxx.xxxxxxxxxxxxxxx.txt (2 points on the name) ?????
2. Maybe caused by a file with a too long name or a too long path ?????

Nobody have a key and some minuts for testing because I need to go next monday at job for formating the key again No PC at home.

ADDED 12h44:
the name of the key is: Crash_log_f (_ = space) and the previous name was DATA

@walkero

Not work: said: 401 Unauthorized !!! Browser not authentication-capable or authentication failed.

hum. not 404 but 401 this time. Is it a feature implemented on OWB allready (log+password) ???. Do that work for you (all) ???

@all

How accessing my modem with OWB ???

With Ibrowse, with http://192.168.1.1, a requester is opened with good login and password. there are no requester with OWB and a page said:

404 Browser not authentication-capable or authentication failed.

Surely, there are amethod to ad the login and password on the http: modem
link.

@Troels

I'm OK for donated something but there are someone able to do the job ???? (Don't know if hard or not).

@MagicSN

No problems. Take care of you and thanks for the work you made for Mame

I'm happy to have donated Verry good

@jahc

- could we use your OWB bookmark program with OWB and having just one bookmark file located on the Ibrowse drawer ????

mean great for OWB and Ibrowse user....

@abalaban

No problem. It's the fact I have understand when reading a second time one of your previous answer

@abalaban

I don't know at all this program but I have a classic amiga also.

If you explain me how using this program (with aminet FTP for example), I could betatest on the classic for you (the next week end for example)

hum, ... you search another developper for the aos3.x version....

@all

Crashed=SAM - PC=PC at job

Key problem checking (on the PC at job):

1. Name (PC): ___LINK. Name (SAM): RALLY2

2. Size (SAM): 276.3 go ???
Size (PC): 1,76go used. 13,1go free all: 14,9go. Size seemed correct on the PC.

3. kind of file (PC): .fab .NG .XBR .0X5. The kind of files on the PC are also corrupted by the content of the crashlog, IMHO.

7. Datestamp (first creation and last modification) (PC):
Lots of 2040-2033-2017-... The datestamp of files on the PC are also corrupted by the content of the crashlog, IMHO.

8. Files (PC): all files and drawers are 0 bytes of size. Even if on the PC, explorer show big size files.

9. A drawer of the Key (PC) have no name. open this drawer and the complete content of the key also on this drawer. another empty drawer. open this drawer and the complete content of the key also on this drawer. and again and again an again.......

Have made a normal FAT32 format with the PC at job and all is fine again.

- First time crashed has been when copied aos4.1 on the FAT32 key with dopus4PPC.

- Second time crashed has been when copied a 20ko crashlog (.txt) on the FAT32 key with dopus4PPC.

Common points:

-FAT 32. (first crash factory formated - second onewith a PC).
-DOPUS4 PPC last beta version.
-I have copied between files from a real PC on the key.

Hope the explanation will help to found the problem (or asking me to do another tests

@broadblues

yes, the 20 ko crashlog file (.txt) content recover all the name of the files previously on the fat32 USB key.

of course the size of the file are wrong also on the key.


- I really would like to contact an experienced person on the AOS4 team for having technical explanation or try to resolve this problem ????


NOTE: BTW, strange thing because dopus4PPC show on the left or right list, the icons with rw_d and if I click on the icons, rawbinfo show me as rwEd. Maybe the problem is on dopus4 PPC ????


Broadblues, I'm verry interested to know how format the key on linux as FAT32 as I have also linux on the SAM !!!

Could you explain that to me ???

@all

see this thread post #11:

http://www.amigans.net/modules/newbb/ ... t_id=34479#forumpost34479

sorry for doubleposting but like that my USB AOS4.1 bugs problem is reported on this thread.

@all

again the same problem

same 16 go usb key with some go of datas inside, formatted with FAT32, from a PC.

Test a program that cause a DSI error. I save the error on the ram: and after think better to make a copy on the usb key.

Using dopus4PPC last version and just copy this only 1 file (20ko) from ram to usb key and key become unreadable

name: Crashlog_Project1-08mai2009-2.exe_2009-05-09_09-05-20.txt (NOTE: 2 (.) on the name of the file).

Size: 21,088 ko

Protected flag: missing the (E) exe flag.

Tool: dopus4PPC last version.

Problem ???: USB, AOS, dopus4, (E) flag, FAT32, 2 point on the name of the file or name of the file too long for dopus4 PPC,......





when seing the pictures, you could see:

right: the file copied to the USB key

left : the damaged result.


and when I read the pictures, all the names of the files finally look like the content of the crashlog !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

yes, confirmed. searching some 8 caracters (left of each 8+3 filename on the grab) and found the result inside the crashlog file (make 5 search and found 5 result on the crashlog file).

thats a verry dangerous problem !!!

Also seing pictures and my 16 GO key contain 276,3 GO !!!

@salass00

Quote:

what is the exact problem. errors when copying and files jump to 8+3 caracters ???

@abalaban

Maybe don't understand if the main program or the simplier GUI. (Read internet with too much speed at work

EDIT: yes, I have made mistakes when reading the first post.