andyinv
Member Since: 23 May 2018
Location: Inverness
Posts: 15
|
Afternoon all
Picked up a cracking HSE Lux 2015D4 the other day, and thought I'd try ripping some of the kids DVDs to a memory stick so they don't have to fiddle with remote controls and DVD menus and such. Worked fine using the Divx converter and Home Theatre profile - but only when I plugged it in to the USB in the front, so it only played in the front. In the back, it didn't recognise the device.
First, is there any way I can throw video on a USB in the front to the rear? I couldn't get it going, maybe was doing it wrong tho..
Or, has anyone ever had a rear USB repaired or replaced, is it one of those things you end up wishing you'd never touched?
Cheers!
|
 17th Apr 2019 11:10 am |
|
|
Weyboat
Member Since: 13 Apr 2018
Location: Weymouth
Posts: 273
  
|
Are you sure the rear usb is not just a mobile phone charging port? Gone 2016 Landmark D4
Current 2015 HSE D4 - AKA - 'Gandalf the Grey'
|
| 17th Apr 2019 7:53 pm |
|
|
andyinv
Member Since: 23 May 2018
Location: Inverness
Posts: 15
|
No, it tries to read it, but says it can't...
|
| 17th Apr 2019 7:54 pm |
|
|
andyinv
Member Since: 23 May 2018
Location: Inverness
Posts: 15
|
Sussed it !
Will work out the exact procedure tomorrow, but I did two things differently just now.
1st, having converted the divx and copying it over, before I ejected the USB, I opened up Powershell and typed rd 'u:\system volume information' -recurse -force
(U: being the drive letter on the PC for the USB drive)
I thought of this, as I'd read somewhere here in the many posts re USB and divx issues that if the player found a file it didn't support, it wouldn't play anything. Although that's a hidden system folder, thought it was worth a go in removing it, as technically, it's the first file in the volume.
Second, instead of trying to control it from the front, under rear system entertainment, instead I put it in limo mode, and selected the USB from the remote control. Lo and behold, up it came..!!
Given that my earlier error was that it couldn't read it, it's most likely that it was the system file causing the problem.
So, tomorrow (or near future), when I'm not half-full of whiskey (hic), I'll work out exactly which of those things fixed it, and write up a full end-to-end guide, might help others out. I see DudleyDisco's post, so will elaborate on exactly what I had to do if it was anything different.
|
| 17th Apr 2019 10:37 pm |
|
|
