IMHO changing LowCyl will have zero effect with CrossDOSFileSystem. With FAT95 or XFSD it should have an effect.
Quote:
BTW: mediatoolbox reports these physical values: 8000 cylinders, 16, sectors, 4 heads And logical size: 64 blocks per cylinder 8000 cylinders...
The physical values from MTB are recomputed for backwards compatibility. No serious filesystem uses them since years. The "physical" values reported by usbdisk.device are one head, one track per cylinder, one block per track, 512 bytes per block, and as much cylinders as blocks. And these are not based on the "physical" values reported by the USB medium, they are based on the reported logical number of blocks only. There also exists a blocksize check, FAT is only accepted with 512 bytes per block, HFS/ISO9660/ FFS/SFS etc is also accepted with other blocksizes.
Fat95 GRs on me (replaced the FileSystem with l:fat95 and tried autosearch mode). Do I miss any compatibility settings?
What is XFSD?
Thanks, Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
Can I tell OS4 to mount the whole device? (like one can mount trackdisk.device, with propper block/whatever sizes/numbers, like telling Linux to mount /dev/sdb instead of /dev/sdb1).
FWW, anything linux does, it's 'affs' is using ADOS3 and OS4 is using ADOS7. I'm sure the arithmatic is different; Dos3<=>Dos7.
10.OS4:> version l:xfsd full xfsd 2.17 (xfsd 2.17 (c) Jul 98 frans)
Search on Aminet for "XFS". I have a partition left on my harddrive, back from the old days, which contains some FAT partitions with a Win95 installation. I vaguely remember that it was tricky to create the mountlists years ago because xfsd does not understand MBR, the LowCyl values had to point to the sector with the FAT bootcode. And the partition had to be inside the 4GB limit. XFSD still works with OS4 here and supports long file names. My mountlist for "PCD":
IMHO changing LowCyl will have zero effect with CrossDOSFileSystem. With FAT95 or XFSD it should have an effect.
Yes I have notices, this where annoying when things does not work as they are suppose to work, I tried mount few different partitions on my PC hard drive whit no success.
The disk contained a none standard partition table, because it contained 2 or 3 primary partitions, and then an extended whit few logical partitions whit in, Linux on some partitions and windows on others.
It nice if the old way mounting disks where supported some how, or if AmigaOS supported MBR format; that way don?t need spend hours wondering way things are the way they are.
(NutsAboutAmiga)
Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps.
Hello I just noticed a strange thing : I'm unable to compile directly on my USB key. In fact gcc seems to compile fine but when it's link time it complains about bad file format for the first *.o on the command line. Looking at the generated objects in FileX show that they are full of zeros...
This behaviour is not known yet, and unfortunately I dont have reliable USB hardware which would allow trying to reproduce it. Which filesystem was used?
It's a standard USB key used as it was when I unpacked it, i.e. not reformated so I assume it's FAT16. I'm using an unfixed XE and except than that read/from from/to this key work reliably.
When the player doesnt contain important data and has an option to format the medium in case he cant understand it, I'd simply try to partition and format the medium from some OS which knows how to create a valid MBR, e.g. Linux or Windows, and not the builtin player firmware...
Ok, got some guts and repartitioned the Swimp3 drive (with fat16 as per manufacturer's recommendation). Used linux for this (x86). Now fdisk doesn't wasrn about anything. Plugged into A1 and it sees it (with either usb stack, final and july's). Copied some files, relabeled the device, and it even plays the files afterwards Huge thanks
Now the IRiver T10:
fdisk reports aetpy:~> sudo fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 1045 MB, 1045430272 bytes 33 heads, 61 sectors/track, 1014 cylinders Units = cylinders of 2013 * 512 = 1030656 bytes Disk identifier: 0x6f20736b
usb.log: I: [6FF6BEA0][hub.usbfd] | Hub port | Device found on hub port 2. I: [6FF6BEA0][hub.usbfd] | Hub port | Device at port 2 is full-speed. I: [6FF6BEA0][hub.usbfd] | Hub port | Device on hub port 2 succesfully added. I: [6AFD8C90][USB Fkt Init] | Init Fkt | Fkt 0x6AEABCD0 is {Vendor: 0x0241, Product: 0x1310, Class: 00.00} I: [6AFD8C90][USB Fkt Init] | Init Fkt | Fkt 0x6AEABCD0 initialized
I'm affraid partitioning it using mbr will prevent firmware reading it. Gone to try it anyway... Edit: Partitioning with MBR didn't help, the only setup the firmware accepts is as fat16 partition taking over the whole space (no MBR). Anyway, freshly formatted (from linux) mbrless device still suffers from the same symptom. Not even a blink in USBMassStorages commodity.
How do I manage to attach it to a usb device driver?
BTW: the product is reported as of same class as mbr-ed SWIMP3.
TIA Jack
Edited by Jack on 2008/1/15 1:13:36 Edited by Jack on 2008/1/15 1:14:37 Edited by Jack on 2008/1/15 11:46:01
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
EDIT: Seems to be a bug in the FAT filesystem, no errors if the Stick uses FFS2.
Really? I thought It was CrossDos... I blowup my SanDisk at least once month. I went to send Rego, recently, a Crash Report for CopyStore and wasn't thinking -- I used drag & drop -- oops. I don't recommend using drag & drop anywhere with USB. Was it FAT, CrossDos, or the text interface?
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
Just for the fun of it i wanted to do a complete build of ScummVM on my ! GB stick, complete with checkout, linking, building and running the exe from the stick.
At least your is recognized as a filesystem. Mine isn't. Except of couple regular lines in usb log, a info window when connecting the device there's nothing else. The usb commodity doesn't see it. A least the other mp3player is recognized. Anyway, if the problematic one will be working under AOS one day, it'll take ages to refill the whole 1GB with music using A1s builtin ub ports Luckily for an ocassional file transfer I have a 1/2GB stick that works in AOS.
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
Hmm, i know this behaviour from my HD's (plugged in through an USB to IDE connector). As soon as they are formatted under WinXP (NTFS, i think) they can't be seen. I HAVE to format them with FAT32 at least.
That's strictly f/s issue imho. Mine is formatted with fat16, no MBR, that's the only combination the firmware likes... I guess I must wait to see if there's any future development with USB support...
Jack
"the expression, 'atonal music,' is most unfortunate--it is on a par with calling flying 'the art of not falling,' or swimming 'the art of not drowning.'. A. Schoenberg
News feed
OS4 Feedback forum
OS4Depot Feedback forum
Amigabounty forum
OpenAmiga forum
AmiCygnix forum
ABC shell forum
AmiKit forum
Cinnamon Writer forum
CodeBench forum
Digital Universe forum
Dopus 5 forum
E-UAE forum
Gnash forum
Ibrowse forum
JAmiga forum
Odyssey forum
OWB forum
Qt forum
SmartFileSystem forum
Timberwolf forum
TouchDevice forum
TuneNet forum
Unsatisfactory Software forum
Donate
