bwillcox

I wasn't responding to anything you posted, it was to jimdukey's post regarding mini and micro USB connections.

I think you are referring to SDs not SSDs. SSDs are the same form factor as 2.5 inch disks and are SATA connected (like most disks).

To be honest, this is the only one I've tried. It is actually one that was replaced by a UDP-203 not to long ago and so moved to my "computer lab" where I could experiment with it w/o disrupting my A/V systems. That's probably a good idea though, to try my thumb drive in the others. Not sure just when I'll get to as I'm currently working on the recovery of a failing file server system and that has taken priority.

Mine is a US model, bought from either Oppo or amazon.com. I don't remember which as I have three of them (in different systems) and not sure which place I bought each of them from.

No other USB devices connected, network connection is ethernet. I will try a different USB drive. Any suggestions on size and/or brand?

I can't flash the firmware to an earlier version as Oppo doesn't allow going backwards from an official release. I could try reflashing with the same level, that should work. Might be worth a try.

Not yet, but I have to admit that I'm out of ideas on what I can try next. I can't see anything wrong with the contents of my thumb drive and yet there must be something I'm missing as it still doesn't work. It's as though the Oppo player ignores it, even though it obviously sees it and does access it (based on display and the flashing light on the drive).

I have compared the ones on the thumb drive to what I downloaded and they do match. There must be something I'm missing but I sure don't see what it is. The files are in a subdirectory named AutoScript, they appear to be correct (size and content), the thumb drive is formatted as FAT32, in a MBR partition. It's a 16GB drive and I don't know how this compares to what others are using. It's a Sandisk drive, which is just about as common as it gets.

I'm in Austin, Tx. That is awfully kind of you, but I really hate to put folks out. This really doesn't seem like it should be that hard. I do wish that if it is actually trying and failing that it (the 103) would put something up in the display about the failure...sigh...

Perhaps, I downloaded the file on one of my FreeBSD systems and then copied it to the thumb drive on a Windows 7 system from a SMB share (where I downloaded it to). I'm not all that familiar with Windows...more of a Unix guy.

Well the file command (what I used to display the file type) may not exist in Windows. It's a Unix command and may only exist in Unix systems and their workalikes (Linux, BSDs, etc.). I remain unclear on the correct size of the sacd_extract file though. Mine is 352,550, and you guys now seem to have two different sizes, 353,550 and 352,550. Of course, then there's the question as to whether or not it matters... The thumb drive that I'm using is a 16GB Sandisk Cruzer.

Hi greynolds, thanks for your response. My USB drive is formatted as FAT32 and the partition type is MBR. I can try it as a exFAT but as far as I've been let to understand, Oppos support FAT32 as well. I notice that your sacd_extract file has a size of 353,550 bytes, yet mine is 352,550. Wonder why the 1,000 byte difference? BTW, the file type of my copy is: sacd_extract: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.27, not stripped Does that match yours?

In case md5 output works better for folks, here that is: MD5 (AutoScript) = 85fcb3f87931eac271aefcfa58ab5c7d MD5 (AutoScript.TSS) = 85fcb3f87931eac271aefcfa58ab5c7d MD5 (sacd_extract) = 14b531b622c92dfe159cf36cff954e5a

Yep, I've done that several times now. The USB stick has a light, it lights up, flashes several times then slowly brightens and dims. The display shows 'USB IN' then switches to 'HOME MENU'. It then stays this way (I've left it like that for several minutes w/o change). I have the correct IP address (actually, it is in my local DNS) in the sacd.cmd file but never get that far. I have disabled both autoplay and resume settings in the player. Here is the sum output for the three files that I have in the AutoScript directory on the USB drive: 15092 1 AutoScript 15092 1 AutoScript.TSS 28122 345 sacd_extract Is 'AutoScript' the correct capitalization for the directory (folder) name? (Linux, like Unix, is case sensitive)? Looking at the sum output, I noticed that the Autoscript and AutoScript.TSS files are identical. Is that expected?

Yeah, that's what I suspected. I don't have them on mine (my USB drive isn't bootable on Windows). What I now suspect (fear?) is that the level of firmware I have on my 103 (latest, BDP10X-83-1226) may be the problem. That would be a bummer.