Quote:

It may also be that the PC address shown in requester is wrong ...

If there are low memory situations involved things causing illegal instruction alerts may be library/devices being flushed which shouldn't be (maybe sometimes caused because of broken lib_opencnt, or libs/devs opened constantly but never closed).

Quote:

Does AROS really use more than 2GB of RAM ?

I was writing this because QBit complained about low amount of free memory displayed on AROS. I did not ask him to remove some of the memory.

Sounds like you might have a faulty memory module .. especially since the problems always occur at the same address or very close.

I changed the Configuration for this PC... I disabled SATA.. reduced the memory to 1 GB and insatalled a 160 GB IDE Hard Disk.....and that makes an enormous change in stability of the System that ^^^ Bug appers... now I will add the RAM again to 4 GB.. to see if that has an Effect on AROS stability!

Quote:

Strange - I will try and replicate the problem.

Quote:

Yes its extremely painful - the handler needs reworked a bit.

Also, when wanderer is listing a subfolder the following happens -:

Wanderer locks the directory -> disk is traversed from the root until it finds the correct entry, which involves linear lookups in each directory (big dirs == slow).

Wanderer examines the directory -> For each file processed icon.library again traverses the disk from its root to find the icon file, performing the same slow linear lookups.

This is the main filesystem bottleneck, however icon.library doing its default-icon stuff with hundreds of entries also is a bit of a show stopper.

Ideally icon.library would be altered so that GetIconTagList knows a new tag (e.g ICONGETA_FileLock) which is an already obtained lock on the icon file, and save a lot of uneccessary processing ... Im also considering deferring Icon loading on my ABI v1 tree so that the main wanderer task opens the window -> fires a child task to enumerate the directory tree (only loading real icons) -> fires a child task to process the window contents loading icons which need to use a default icon (or using the thumbnail plugin) as appropriate.. which should result in the wanderer window being more responsive, the icon list itself coming up quicker, and with the afore mentioned icon list change - the whole process being considerably faster.

As for NTFS handler - there's a lot of things that need to be done to speed it up =) NTFS stores directory contents alphabetically sorted using btree+

The current way that NTFS is implemented could also be much refined - with locks becoming real instances of NTFS MFT records (which would clean up and simplify the code/handling considerably).

I would like to address those issues before contemplating adding write support...

qkalmatee

I installed Icaros 1.4 ... that Version doesen't have a NTFS Hamdler.. the crashes appear anyway.... I'll wait until next crash and then I'll show you.... there is only Work and AROS present... and this PC 0x.... Bug appears anyway,,,,, as I tried out with all Drivers disabled.. it may be a SATA Bug.. because most of the Time it is ATA(Pi) crashing.... but I have still anopther Option... I have a plain AROS Install on a IDE Hard Disk.. I will try too boot AROS from IDE and remove all SATA Drives!

@paolone..... well,,,, it took me some time to find out how to even format 1 TB Drives in Fat32..... the Problem is.. I did becaise I bought some day a few yeaers ago a Media Player Box which only could read FAT32 and it worked well.... the other thing is.. that I am playing with AROS for a few years.. O.k.. I can't contribute very well but e.g the Fat32 formatted Drive (where I have my Media Files from my Media Box) was the only Possibility to transfer Files from Windows to AROS... I could install AmiKit on AROS.. listen to Music... Download Files daster with Windows and transfer them to AROS.... I don't care if I have less Diskspace.. 1 TB is lot anyway.. but it was the most feasable solution.

Quote:

So you have a 1 TB and a 2 TB FAT-formatted drives? o_O

FAT32 is a very inefficient filesystem on large drives. I'd probably not format anything beyond 32 GB with it (choosing NTFS instead). Microsoft has recently enabled FAT32 to support bigger drives with a extended filesystem (FAT32-EXT) which is not compatible with most 'foreign' FAT32 implementations, I'd not be surprised if AROS one doesn't support it.

The main problem you may encounter with FAT using large drives, however, is wasting a lot of space with oversized clusters. You may waste 64KB of space for every little file you have on the hard drive. If you don't need to read data from AROS or other operating systems, I'd suggest you to convert your big FAT32 partitions into NTFS ones (beware: can't be reverted with system files).

Quote:

That reminds me: while trying out the NTFS handler, I noticed that (at least in some cases), not all of a file was copied from an NTFS volume (e.g. with "Copy System:blah T:"). When I copied the sample sunset.jpg file included in "My Pictures" in XP, the bottom right-hand corner was corrupt.

Also, when I opened System:WINDOWS in Wanderer, I had to switch off the computer after waiting about half an hour for the files to be shown. However, I know slow directory listing is a known issue.

I will do a install from Scratch to check if it is Malware related! *smile*