← VBar NEO for external transmitters

Win 10 Pro & Home sees unit as a USB hard drive. Unable to change translated

VBar › VBar NEO for external transmitters · Started by Bob H on 16 July 2017 11:3816.07.2017 11:38
Bob H 16 July 2017 11:3816.07.2017 11:38
Hello,

I've finally have the opportunity to use a vBar NEO that I bought at the BMFA Nats last year from Fast Lads.

The long and the short of it is that both my desktop (Win 10 Pro) and laptop (win 10 Home) will not correctly recognise the unit as a vBar but keeps seeing it as a USB hard drive called "vboo t". Further, both systems refuse to allow me to manually change the driver over to the correct vstabi driver, insisting that the unit is a USB hard drive and that it's being connected via a USB 3.0 port. It's not. My laptop doesn't have any USB 3 ports for starters. I just can't get any of the vstabi software to talk to the unit as the unit seems to be adamant it's a hard drive and not a flybarless unit.

Is this unit dead on arrival? Please advise.

Thanks in advance,

Bob H.
RV 16 July 2017 21:1116.07.2017 21:11
Well - first check if the boot plug is only used for update and not for setup.

If it won't work - and having W10 creators update ... read here:

http://www.vstabi.info/en/node/2182

regards (EN) / Gruss (DE)

Rainer Vetter

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Posting and answering - please use a PC and a standard keyboard. Answer all questions fully, take the needed time, don't forget probably requested attachments.

Für Posts und Antworten bitte einen PC und eine richtige Taststaur benutzen sowie alle Fragen vollständig abarbeiten. Nehmt Euch Zeit, beantwortet Rückfragen in Ruhe und vollständig.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Für Einzelkommunikation bitte ausschließlich Email verwenden! - PN, Messenger, Chat usw. werden nicht bearbeitet.
For single user communication please send a email only! PM, Messenger, Chat etc. won't be read.




1 mal bearbeitet. Zuletzt am 16.07.2017 21:11 von RV.
Bob H 2 September 2017 11:2202.09.2017 11:22
No matter how I try this with VirtualBox it still doesn't want to work.

VirtualBox either comes back with nothing or the following set of return strings when I plug in my NEO:

On first connection with Virtualbox
[ **] FAT-fs (sbd): unable to read boot sector to mark fs as dirty
[ **] sd 0:0:0:0: [sbd] No Caching mode page found
[ **] sd 0:0:0:0: [sbd] Assuming drive cache write through
VStabi VStabi Pioneer of Flybarless