The players are not under warranty so I doubt that they will help but I suppose I could try all the same. Thanks for the tip.Bootdog said:Did you try calling them, and asking to speak to someone in the tech department in Dublin? They are based in Citywest if I'm not mistaken.
I found them very helpful in the past, they organised a swap for me when I called out to the factory with a Zen Xtra 60 GB that was defective from new.
Thanks. I'm familiar with how the players work having an old [broken link removed] myself and all the latest Creative software (MediaSource Player/Organizer, NOMAD Explorer, Jukebox 3/Zen Xtra drivers etc.) installed. In any case the issue is not access to the player from the PC (via the Creative software - I realise that the player doesn't appear as a normal USB/FireWire mounted drive) that's the main problem but rather the fact that the player won't boot properly from the hard disk even though there doesn't seem to be any low level problem with it - i.e. it seems to be a problem with something like the proprietary filesystem on the disk itself that the Clean Up operation can't cope with because the Fujitsu and other low level diagnostics report no problem with the physical drive.I presume the nephew told you that it won't work without the Nomad Explorer software installed (i.e. its not simple plug and play).
On writing NJB filesystem-like components:
Users of Unix-like operating systems in particular have a nack to
turn everything into filesystems. Naturally, many people believe that
the best way of accessing the jukeboxes would be through a filesystem
component, which is indeed also the way that USB mass storage-enabled
devices like the Nomad MuVo and other peripherals like digital
cameras do it.
The problem with the Nomad Jukeboxes is that they are actually not
filesystems: internally, the jukeboxes are databases. The Apple iPod
is engineered very much the same way. Thus, a "file" in a nomad
jukebox consists of a database entry with several metadata
components, such as artist, title, original filename, and the actual
MP3/WAV/WMA-file is just a binary large object (BLOB) in this
database entry. Such a database structure is not easily reflected
as a filesystem: when reading files off the device this is easy
enough, but when *writing* files, all relevant parts of the metadata
has to be added to the database. This means that a filesystem
component that is capable of writing to the jukebox would have to
include something like an ID3 tag parser to extract metadata from
the file and insert this into the database.
...
Database format:
The internal format of the database(s) used to store tracks,
files and playlists on the series 3 devices is actually known:
when listing the files on the device, an odd file with a 16-byte
serial number appears in the directory. This file actually
contains the file database so it can be examined. (We don't know
why it's there, perhaps for debugging?)
A typical beginning of the file will look like this:
0000: 0100 0100 0000 0000 0000 0e00 0000 0600 ................
0010: 000c 001c 620f 0600 000e 0928 0000 0600 ....b......(....
0020: 0016 78ca 7441 0600 0018 2000 0000 2000 ..x.tA.... ... .
0030: 0007 7200 6500 6700 6c00 6500 6d00 6500 ..r.e.g.l.e.m.e.
0040: 6e00 7400 6500 7400 2e00 7000 6400 6600 n.t.e.t...p.d.f.
0050: 1400 000d 5c00 4600 6f00 6f00 5c00 6200 ....\.F.o.o.\.b.
0060: 6100 7200 5c00 0000 0600 000c 001c 6218 a.r.\.........b.
...
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?