TeraByte Support wrote:> the .bus member ?> > > "tas3086" wrote in message news:11461@public.tbosdt...> > Is there a function or utility in tbos like GETHDINFO and GETDRVLTRINFO, > that would allow the detection of information for USB connected drives?> Thanks in advance.

Having started TBOSDT on Windows 10 (64 bit), I can cd to J:, and runtbs a script that includes the gethdinfo function. All sata drives are listed, but not the CD/DVD and USB drives, including J:, a drive that has 4 partitions.

It should be noted that running (exec imagew) under tbosdt will see the J: drive as an available backup drive.

What are the drive numbers as shown in drive management (is there a large
gap) ?

"tas3086" wrote in message news:11465@public.tbosdt...

TeraByte Support wrote:
> the .bus member ?
>
>
> "tas3086" wrote in message news:11461@public.tbosdt...
>
> Is there a function or utility in tbos like GETHDINFO and GETDRVLTRINFO,
> that would allow the detection of information for USB connected drives?
> Thanks in advance.

Having started TBOSDT on Windows 10 (64 bit), I can cd to J:, and runtbs a
script that includes the gethdinfo function. All sata drives are listed, but
not the CD/DVD and USB drives, including J:, a drive that has 4
partitions.

It should be noted that running (exec imagew) under tbosdt will see the J:
drive as an available backup drive.

Disks 0-3 are sata 4-5 cd/dvd 6-7 are USB 8-9 are sata on a second controller

It should be noted that tbexplo.tbs finds/sees the usb's.

Additional information.:It seams that if the system is booted with all drives connected, then gethdinfo will work. If USB drives , or hot swap sata drives are connected after boot, then gethdinfo will not see the devices. Not 100% sure, but did see a change with one test.

Absolutely correct. I used the example that was in the manual, unfortunately that example stops when a CD/DVD device is detected. You need to continue checking if you want to get all devices. Too bad that there isn't some other easy way to determine when you get to the end of the device chain. A value of 64 took perceptibly longer to complete, but is probably more accurate that my value of 15 !!