@tonyw

Quote:

Great!! (and lots of issues IMHO)

Quote:

This is really strange because with asyncWB disabled (or NOASYNC or NOCOPY), I have successfully copied 3 times a big file on a 16go FAT32 key (and I have never managed to copy one big file on a FAT32 16go USB key before).

Are you sure this fact not show another not known problems ??? (big files on big medias with FAT32,FS,FFS). Remember kas1e also report this problem on SFS and FFS.

I have planned to open a new thread on the AOS4 feedback thread about FAT32 (just for explaining my point of view about bad FAT32 on AOS4). IMHO FAT32 suffereing a lot of problems and another thread just for FAT32 will be usefull to manage.

Quote:

No problem, I'm sure now with elwood and you, this problem will be resolved for the next release

Quote:

FAT32 is important because for sharing datas between differents OS and for the credibility of AOS4.

IMHO Problems are:

- corrupted datas during copy on FAT32: 8+3 filename+ big size on the medias.
- Big datas copied give memguard on FFS,SFS,FAT32.
- FAT32 need to be verry improved.

Thanks Tonyw to said that I have been usefull for something. Thats great for me

@all

Bump

@ZeroG

FAT sector size of 512, 1024, 2048, 4096 bytes.

Apparently, windows choose a default depending of the size of the hardware.

I surely must choose the exact value before formatting (4096 bytes for 2x250 Go) that choosing the default value on the format window on the PC.

but I'm not sure.... I haven't a PC at home....

@all

I have my drive and going to a friend this afternoon for formatting the drive on the PC with Seven.

I have splitted my drive to 2 FAT32 partitions on the PC.

On the amiga, the 2 partitions are recognized but he has choosen a cluster apparently not supported by AOS4.


Seven show lots of differents cluster size and XP just show: cluster by default.


Questions:

- What is the cluster size supported by AOS4 and AOS3 and AROS (the common size) ????


- Could we add to AOS4 the support of lots of cluster size for FAT32 and available on seven ???

@all

OCZ rally2 16go, formatted with FAT32 with a PC, this morning at job, and copy 3 times 16go on the rally2 with the PC (and format in FAT32 between) to be sure the media is fine (and effectively no problems on the PC).

On the SAM+AOS4.1U2:

TEST1:

copy a 850mo files on the USB rally2 key with a drag'n'drop icons.

The copy start fine but same problems.

See the 2 grabs.


8192 bytes:



16384 bytes + AsyncWB.



- The USB stack reset for the OCZ medias 3-4 times and during each reset, the memguard hit that mean this is USB the problem surely.

TEST2:

Just after the test1, I have made the same but only remove the AsyncWB tool (loading during the boot and managed with prefs/wbstartup).

I have drag'n'drop the same files and the copy work fine UNTILL THE END !!!!!!!!!!!!!!!!!! YEAH !!!


AsyncWB not running mean It's not possible to do other things during the copy with the Amiga but this first copy work fine !!!!!.


TEST3: (also without AsyncWB)

The same as TEST2 and this time use DOPUS4 and.... the copy work fine also !!!!

As the workbench run completely during the copy, (surfing at the same time of the copy), the fault is: AsyncWB !!!.


TEST4:

Let AsyncWB running, and just add NOASYNC (as a tooltype), and the copy work fine also.

TEST5:

Let AsyncWB running, and just add NOCOPY (as a tooltype), and the copy work fine also.


RESULT: AsynWB cause problems during the copy of datas on FAT32 medias. Add NOCOPY tooltype on asyncWB Tooltype solve the problem.

@all

I have copied the same file on my 1go USB stick (formatted on a PC), with Dopus4, without problems.

I will do the same test, with my 16go key FAT32 formatted on the PC, with the AOS4 copy command, this end of day.

I actually fill my 16go key with datas on the job's PC (for checking the media).


@Elwood

If formatting medias with FAT32 on the SAM should not be used, why is it possible to format FAT32 ???? (Remove this feature untill FAT32 will be well tested IMHO).

@abalaban

I haven't remplaced the ..... kernel debug kmod (don't remember the exact name) on my machine for debug101.

The test is made with a cold boot and just put the USB hardware, open dopus4 and start a copy. (This problem exist long before debug101 exist).


- I have just formatted my 1go USB key on the PC (at job) and will made the same test after the job (to check if 16go key cause the problem).
- I will made the test without keyboard and mouse plugged (to test if my USB hardware cause the problem).

@tonyw

- I have formatted my OCZ 16go key with XP, at job, this midday.
- I boot the SAM and launch dopus4 and copy a 850mo files from the amiga to the USB key.

the copy run a little and the memguard hit.

- If I use retry or cancel, a new memguard hit came and the USB stack restart, (as if I have just inserted the key).

- If I use cancel, finally a requester said:
the integrity of the copy is damaged, continue at your own risk (or something like that).

A grab at the start of the problem:




Please notice:

- I use a 16go USB key.
- fresh formated FAT32 with a PC at job.
- Just copy one file with the amiga on (file 850mo).
- This memguard hit is important and mean something because it reset the USB stack (or reset the OCZ media only).


USB problems with FAT32:

1. Use my OCZ 16go key for copy some small files (like the workbench) and an error occured and datas on the key become 8+3 with crazy high size

http://www.amigans.net/modules/newbb/ ... =ASC&type=&mode=0&start=0

2. Use my OCZ 16go key for copy one big file, and this thread about the memguard hit.

TonyW, could you make some tests with a big size USB media ??? (It's more easy for you because you test USB2).


I have a PS2->USB adapter with a PS2 keyboard and a standard 3 boutons USB mouse logithech. All work fine and no problems.



EDIT: another test:

I have just baught a 500go 2.5" USB2+esatap external Harddrive.

Just Trying to fomat to FAT32 with the SAM (after waiting long minuts because USB1) and:



A new memguard hit, same as previously but with 16384 this time (with the HD).

Don't know but... earing about cluster 8ko and 16ko for FAT32 ???


SFS: Warning: Task 0x59a84130 ("OHCI Controller Task Unit 1") called DoPkt()
SFS: Warning: Task 0x59a84130 ("OHCI Controller Task Unit 1") called DoPkt()
SFS: Warning: Task 0x59a84130 ("OHCI Controller Task Unit 1") called DoPkt()
SFS: Warning: Task 0x59a84130 ("OHCI Controller Task Unit 1") called DoPkt()
SFS: Warning: Task 0x59a84130 ("OHCI Controller Task Unit 1") called DoPkt()

MEMGUARD HIT - "OHCI Controller Task Unit 1" (59a84130)
allocation of 16384 bytes by AllocVecTagList() failed
0: 6f4fbbe4 59a4ed90 00000000 01ca97c4 00004000 59a4ee18 5b787e38 5cd5a000
8: 00004000 00000008 01ca97c4 0000407f 24000088 00000000 00000000 00000000
16: 00000000 00000000 5cd5a000 59c75970 59a37680 00004000 01e70000 5ff9a8c0
24: 00000000 00000040 59a50a88 59ac1e30 00000000 00000040 00000081 00000003
----> 6f4fbbe4 : "MemGuard" segment 0005 offset 8bdc
----> 01ca97c4 : "Kickstart/kernel" segment 0001 offset 497c0
----> 01ca97c4 : "Kickstart/kernel" segment 0001 offset 497c0
----> 01e70000 : "Kickstart/newlib.library.kmod" segment 0001 offset 061c
LR 014136f0 : "Kickstart/kernel" segment 0000 offset 136ec
CTR 6f4fbbe4 : "MemGuard" segment 0005 offset 8bdc

Stack backtrace:
----> 014136f0 : "Kickstart/kernel" segment 0000 offset 136ec
----> 018c7abc : "Kickstart/ohci.usbhcd" segment 0000 offset 5558
----> 018c5274 : "Kickstart/ohci.usbhcd" segment 0000 offset 2d10
----> 018cc2c8 : "Kickstart/ohci.usbhcd" segment 0000 offset 9d64
----> 018cc448 : "Kickstart/ohci.usbhcd" segment 0000 offset 9ee4
----> 018c9d74 : "Kickstart/ohci.usbhcd" segment 0000 offset 7810
----> 0141587c : "Kickstart/kernel" segment 0000 offset 15878

Disassembly:
014136ec: 4e800421 bctrl
014136f0: 80010084 lwz r0,132(r1)
014136f4: 38210080 addi r1,r1,128
014136f8: 7c0803a6 mtlr r0
014136fc: 4e800020 blr

@abalaban

Thanks for the explanation. I could test (hum....use) debug101 finally

@kas1e

Quote:

????? Because I really really would like to use this tool with the next AOS4 version

I don't own AOS4.0, just AOS4.1 and more...

@alfkil

Quote:

Do you have reported this problem to the AOS4 developpers or on the AOS4 feedback thread, on amigans ?????

@tonyw

Quote:

This is not impossible. Also people said that It's better to formatting FAT32 on the PC than on FAT. It's necessary to do that for hardrives (compatibility problems) and not surely for USB stick also.

Quote:

@elwood

theoricaly, the memguard hit appeared for this case.

@Elwood

Don't know what is a seek failure but run your test with memguard enabled (story to see if the memguard I report often - post #1 - is also allways present).

Thanks for testing this problem (I can't do that myself and you know why

@all

Joerg hasn't a functionnal Amiga-NG actually, isn't it ???

@all

last question:

- Is it possible to make more than one partition on the Harddrive ????

- Poseidon on AOS3, sirion on AOS4, AROS, linux.... all manage fine to use Harddrive with more than one partition ??

I don't want to copy the stuff on the HD with more than one partition and see after another system don't manage well the thing

@alfkil

first test (don't worry

Hum, Just remember that testing on AOS4.1U2 not work fine.
Verry sorry......

Just for curiosity


Executable section (0x1000074/3760392 bytes) starts at 0x6efef020
Relocating section ".stab" (index 23) which is referred by section ".rela.stab" (index 24)

and a DSI:

Crash log for task "db101"
Generated by GrimReaper 53.2
Crash occured in module elf.library.kmod at address 0x015320F8
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 0001656C 5975C5B0 00000000 00E41D3C 01529FEC 01503924 01503924 00000000
8: 00B30000 0000000C 00B30000 014154A8 24002048 5995D8B0 00000000 5A8C3EBC
16: 58B9A22C 58E7BBE0 5B454680 01CA97C4 00000000 58E7C940 58B97344 5A8C31D4
24: 5B454680 5975C608 00000000 80000001 00000000 58E7BBE0 0152B6F4 59669C40


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 2.45825e+24 1.64779e+93 3.15834e+231
4: 3.91208e+107 1.06281e+94 9.92552e+170 7.51825e+199
8: 3.15637e+21 4.91013e+252 2.16225e-307 1.26282e+200
12: 6.97271e+228 1.75792e+199 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 1.04023e-162 0 0 0

FPSCR (Floating Point Status and Control Register): 0x82000000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x44002042
Instruction Pointer (ip) : 0x015320F8
Xtended Exception (xer) : 0x20000008
Count (ctr) : 0x014154A8
Link (lr) : 0x015320F0
DSI Status (dsisr) : 0x00000000
Data Address (dar) : 0x00000008



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x015320F8 belongs to module "elf.library.kmod" (HUNK/Kickstart)

Stack trace:
native kernel module elf.library.kmod+0x000081f8
native kernel module elf.library.kmod+0x000026e8
native kernel module elf.library.kmod+0x000061f4
db101:amigaos_relocate_elfhandle()+0x384 (section 1 @ 0x914)
db101:load_inferior()+0x47C (section 1 @ 0xe14)
db101:gui()+0x1260 (section 1 @ 0x3a90)
db101:main()+0x24 (section 1 @ 0x1608)
native kernel module newlib.library.kmod+0x00001f4c
native kernel module newlib.library.kmod+0x00002be0
native kernel module newlib.library.kmod+0x00002d5c
db101:_start()+0x170 (section 1 @ 0x170)
native kernel module dos.library.kmod+0x0001b524
native kernel module kernel+0x00036290
native kernel module kernel+0x00036310


PPC disassembly:
015320f0: 813d0024 lwz r9,36(r29)
015320f4: 801f0030 lwz r0,48(r31)
*015320f8: 817c0008 lwz r11,8(r28)
015320fc: 7c004b96 divwu r0,r0,r9
01532100: 935c0004 stw r26,4(r28)

@all

OK. With an harddrive (contrary to an USB stick), it's not possible to:

- Use an amiga to create FAT32 partition(s) because the PC won't recognize the drive.

Need to use a PC and with a special tool for FAT32 more than 32go, like Fat32Formatter.

- Mix FAT32 and SFS because PC and amiga filesystems overwrite each other (simple explanation).


This 2 questions are unanswered:


I have planned to put first on the SAM and after on an external Harddrive case. The benefit is to use SATA directly for gaining copy time with the amiga on FAT32 partitions.

- Can I put a complete FAT32 HD on an amigaNG computer and boot fine with this HD ??? (FAT32 recognized,...)


In case a media is SFS AOS4 formatted:

- SFS AOS4 is compliant with SFS 68k ??? (for sharing between SFS 68k and SFS AOS4)


@tonyw

do you think that there a a possibility that FAT32 and SFS could be together with recent Windows OS ???

I have just orbered the hardware, I maybe could made some test (if not allready a lost of free time if someone esle has tested recently)....

Hello,

I have planned to buy a new HD 2.5" 500go. for sure, this HD will be formatted with NTFS. My first solution is to prepare this HD with HDtoolbox and format to FAT32 (all with the amiga).

I would like at least to split the HD to 2 parts, both with FAT32 or half with FAT32 and one with SFS.

Questions:

- Can I use HDtolbox to split the HD and use FAT32 for one or more part of the HD ???

- FAT32 from AOS4 is compliant with the FAT32 PC version ??? (Allready try with an USB key but never with an Harddrive).

- Can I have one FAT32 and one SFS at the same time ???

- Can I use safely the medias on PCS after ???


I have planned to put first on the SAM and after on an external Harddrive case.

- Can I put a partly or complete FAT32 HD on an amiga computer and boot fine with this HD ??? (FAT32 recognized,...)

- The SFS filesystem from AOS4 could be recognized on a classic amiga ???


Miscellaneous question:

- What is the maximal FAT32 partition size ???

- What tool can I use to format the Harddrive on the PC ??? (as far as I know, the PC can't format more than 32go).


Yes, I would like to have the HD partly or completely FAT32 formatted for compatibility with others computers.

@kas1e

I like Muforce on AOS3.x because I run it on a script and I send the catched hit and the programmer resolve the problem (generally and verry often).

With AOS4, It's not the case and the programmer have dificulties to found the problem. Grim reaper not work well allways and sometime AOS4 freezed without grim reaper (boring) and sometime the programmer is lost with the Grim reaper, GDB not uptodated, memguard exist but, for example, when the memguard hit for USB copy, nobody know what happened with this memguard,etc.....

I'm searching desesperately after a debug tool, launched on the background who catch ALL problems and are able to save the output for the developper. An output with ALL necessary inside to found the problem.

As you have seen, no technically langage programamtion sentences since the beginning of this answer but I really would like to save the freetime of the programmers with a gret output when a problem arrive with an AOS4 software.

If debug101 and/or valgrind could be a candidate for this task, I could fill a lot a bounty I can't help by programming but I could help with some money..


But the problem isn't the bounty because It's more easy to found money than an AOS4 programmers with skil and free time.....