- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- DeviceIoControl() and Autoloader 1/9
StoreEver Tape Storage
1748235
Members
3519
Online
108759
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2001 01:08 PM
тАО10-25-2001 01:08 PM
DeviceIoControl() and Autoloader 1/9
Hi
I am trying to write an application that is able to issue commands to the autoloader through the Win32 DeviceIoControl() function. I am not having any success. I can open the ultrium tape drive with CreateFile and read/write to it.
Win2000, PIII 1GigHz, Ultrium tape drive and Autoloader 1/9 with lto tapes.
HP Tape Tools finds the Autoloader and can issue commands to it in the tests ...
My questions are:
Do I need to open the Autoloader as if it was a separate device, i.e. get another HANDLE (i don't know the device name if this is the case)? I initially thought I could open the tape device (\\.\Tape0) and then use that handle to access the autoloader with deviceiocontrol.
Does HP have any documentation/examples of using win32 DeviceIoControl with their Autoloader 1/9?
Thanks
Jonathan
I am trying to write an application that is able to issue commands to the autoloader through the Win32 DeviceIoControl() function. I am not having any success. I can open the ultrium tape drive with CreateFile and read/write to it.
Win2000, PIII 1GigHz, Ultrium tape drive and Autoloader 1/9 with lto tapes.
HP Tape Tools finds the Autoloader and can issue commands to it in the tests ...
My questions are:
Do I need to open the Autoloader as if it was a separate device, i.e. get another HANDLE (i don't know the device name if this is the case)? I initially thought I could open the tape device (\\.\Tape0) and then use that handle to access the autoloader with deviceiocontrol.
Does HP have any documentation/examples of using win32 DeviceIoControl with their Autoloader 1/9?
Thanks
Jonathan
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2001 12:00 PM
тАО10-30-2001 12:00 PM
Re: DeviceIoControl() and Autoloader 1/9
There is no official documentation for the problem your trying to solve.
A few tips:
You must open the autoloader device separately. They are independent devices. On Win2K/XP you must use the Changer device to open the device for all recognized libraries. On NT or on Win2K/XP with unrecognized libraries you must use the PhysicalDevice to open the device with the OpenFile call.
You may have to query the HBA information to obtain a list of available devices and to find out which index to use on the device.
The best resource for information on how to program this is the Microsoft MSDN library.
A few tips:
You must open the autoloader device separately. They are independent devices. On Win2K/XP you must use the Changer device to open the device for all recognized libraries. On NT or on Win2K/XP with unrecognized libraries you must use the PhysicalDevice to open the device with the OpenFile call.
You may have to query the HBA information to obtain a list of available devices and to find out which index to use on the device.
The best resource for information on how to program this is the Microsoft MSDN library.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2001 12:38 PM
тАО10-30-2001 12:38 PM
Re: DeviceIoControl() and Autoloader 1/9
Thanks for the tips.
Can you also give help on determining the name of the device to use in the open call. Typically the device names are \\.\c: or \\.\Tape0, but I don't know the device name of the autoloader (and can't find it on MSDN). I am not very familiar with SCSI devices. Is there something like \\.\SCSI0?
Where can I find the device name?
Any help is greatly appreciated, thanks.
Jonathan
Can you also give help on determining the name of the device to use in the open call. Typically the device names are \\.\c: or \\.\Tape0, but I don't know the device name of the autoloader (and can't find it on MSDN). I am not very familiar with SCSI devices. Is there something like \\.\SCSI0?
Where can I find the device name?
Any help is greatly appreciated, thanks.
Jonathan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2001 03:37 PM
тАО10-30-2001 03:37 PM
Re: DeviceIoControl() and Autoloader 1/9
Valid names are:
\\.\PhysicalDrive0 (...)
\\.\Tape0 (...)
\\.\Changer0 (...)
\\.\SCSI0 (...)
\\.\PhysicalDrive0 (...)
\\.\Tape0 (...)
\\.\Changer0 (...)
\\.\SCSI0 (...)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP