Hi JB,
-= JB =- wrote:
Hi Phil,
I tried it and when I click the button to list the USB drives
the field on the left gets a blue selection line at the top
and nothing else happens.
That means the library didn't find any mounted USB mass storage devices.
In fact it was your code to list the USB3 devices in the
Scripter's Scrapbook that I got the shell command from.
That code would not work for me either.
I have Mac OS X 10.4.11 on a G4 AGP.
thanks, if you know how to fix it I would be interested.
Another thing. do you know how to access a USB device
with only the info it gets.
Not really, unless the volume name is included in the library output.
How do you properly write the
line to access it. I know when I list the drivers I have a
keyspan serial and the info the system profiler provides
is not the same as if I list the drivers. I am pretty sure I
need to use the info from listing the drivers. Is the thing
it needs to show as a volume or be listed with the drivers
to be able to access a USB device that shows up?
-=>JB<=-
Drivers are useful if you're trying to interact with a USB
communications class device (like a USB board that controls some
external machine or process), but not if you want to read/write data
to/from a USB mass storage device.
Some USB mass storage devices (specifically some digital cameras) use
Picture Transfer Protocol (PTP) to transfer images to computers; devices
that use PTP don't show up in Revs "the volumes" list.
Here's a function based on one written by Dar Scott & Ken Ray a few
years ago. It will give you more info about available drivers than
driverNames(). I use it to detect what USB communications class devices
are connected. Maybe it will help. Watch for line wraps!
function deviceNames
switch the platform
case "MacOS"
return _macDeviceNames()
break
default
answer "Not supported."
exit to top
break
end switch
end deviceNames
function _macDeviceNames
local theNames="", ioregOutput, skipLines, temp
local IOTTYDevice, IODialinDevice, IOCalloutDevice
set the hideConsoleWindows to true
put shell("ioreg -n IOSerialBSDClient") into ioregOutput
repeat forever
put lineOffset("IOSerialBSDCLient",ioregOutput) into skipLines
if skipLines is zero then return thenames
delete line 1 to skipLines of ioregOutput
-- Get all the data between the braces
put char(offset("{",ioregOutput)) to (offset("}",ioregOutput)) of
ioregOutput into temp
get matchText(temp,"\"IOTTYDevice\" = \"(.*?)\"",IOTTYDevice)
if it is not true then next repeat
get matchText(temp,"\"IODialinDevice\" = \"(.*?)\"",IODialinDevice)
if it is not true then next repeat
get matchText(temp,"\"IOCalloutDevice\" = \"(.*?)\"",IOCalloutDevice)
if it is not true then next repeat
put IOTTYDevice,IODialinDevice,IOCalloutDevice & lineFeed after
theNames
end repeat
end _macDeviceNames
On Jul 31, 2008, at 3:48 PM, Phil Davis wrote:
Hi JB,
Try this:
http://pdslabs.net/stacks/libUsbDrive.rev.zip
It uses system_profiler on the Mac to get drive info, but presents it
more succinctly.
Phil Davis
-= JB =- wrote:
This will provide some info about the USB on Mac OS X;
on mouseUp
put shell("system_profiler SPUSBDataType") into tProfile
put tProfile
end mouseUp
-=>JB<=-
On Jul 30, 2008, at 5:13 PM, -= JB =- wrote:
Maybe that is not the answer. I found out it shows network
all the time when I use put the volumes.
So how do I identify a list of USB devices?
-=>JB<=-
On Jul 30, 2008, at 5:08 PM, -= JB =- wrote:
Here is the answer:
put the volumes
-=>JB<=-
On Jul 30, 2008, at 5:02 PM, -= JB =- wrote:
I realize my question below was not asked properly because I
should have said USB devices and not drivers.
Use the open driver command to communicate with usb devices,
devices attached to a serial port other than the modem and
printer port, and other peripheral devices.
I would like to know how to find the names of USB devices hooked up
to my computer.
-=>JB<=-
On Jul 30, 2008, at 4:18 PM, -= JB =- wrote:
I can get a list of the available serial drivers by using the
driverNames.
How do I get a list of USB drivers?
-=>JB<=-
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
--
Phil Davis
PDS Labs
Professional Software Development
http://pdslabs.net
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
