Как получить доступ к параллельным портам, созданным командой NET в Windows XP?

Ok. So you connected a parallel device/printer via a "USB-to-Parallel IEEE-1284"-cable to the USB-port of your computer. Now you need to directly communicate to it. I understand you can't change the software directly to communicate with modern ports like USB001 etc. like the drivers of scanners do. And the software you have needs to communicate by normal protocol for old-LPTx ports (i.e. 0x378 instead of LPT1 etc.)

That leaves you with one option and that is "emulation". This should be done by the driver which came with the "USB-to-Parallel IEEE-1284"-cable. This driver should make a LPTx port and capture port-communication etc. But most (if not all) of these adapters come with drivers who emulate an USB-printer. In most cases this is the easiest (and even in case of old DOS-programs this can be solved with a NET command) but when it comes to real port-communication it is useless.

So you need to find a program that can emulate a LPTx (and its ports) and bidirectionally communicate with (any) USB-driver on your computer. I have not found one (yet).

The only thing useful i found was this Converter From USB To Parallel. This one emulates the LPTx and ports and communicates directly with the adapter. I have not tested this myself but the info-page looks promising. From the help-file:

The USB2LPT device and its driver enables redirecting of port access by random application software to a USB-attached parallel port, i.e. emulating a parallel port via USB. This unique solution works on all USB supporting Windows operating systems.

It does label its own driver as "Driver unstable" but you'll get the idea for what you're looking for. It also needs a special USB2LPT-adapter though. From its faq-page:

Q3. Can I use the USB2LPT.SYS driver with a regular (cheap) USB to parallel printer adapter? A. Of course not! It's never possible due to design limitations of such adapters. See below. 

It also lists as a minus for itself its Reduced speed due to emulation (expect 10..100 times slower). But it will allow communication with Base address same as built-in (378h, 278h). If you like you can make your own adapter. The schematics are all on the site. Here you can find complete instructions (including videos) on how to build one. Or else you can mail him for details on how to get one.

I think that you may be going about this all wrong. You should not be using "NET USE" but rather using the adapter's software driver to associate a virtual printer port with the USB port. Rik has posted a screenshot of how this works. Only if the adapter's software allows it, should you then be able to write as if that physical port existed.

The NET USE LPT1 command that you showed is for when you connect to a printer on your own or another computer, and set that printer as your local (LPT1) printer. It is based on printing to the device name LPT1 and then redirecting that, which you have said your software won't do (requiring a hardware port).

Here is a driver from Startech, that makes some of these cables, but I don't know if it will work for you; it does work with some other models (including ones that I've owned): http://sgcdn.startech.com/005329/media/sets/ASIX_MosChip-MCS7715_Drivers/ASIX_MCS7715.zip

In the meanwhile, get rid of that NET USE command; it's really not helping you right now, and if you could get it to work at all with the local printer, would still require you to be writing to the LPT1 device (not to the hardware location where it would be, if only it existed.)

You will need the .NET-Framework and PowerShell, but with this script, you can get access to a list of any Parallel-Ports installed on your system.(+Additional informations)

$strComputer = "." $colItems = get-wmiobject -class "Win32_ParallelPort" -namespace "root\CIMV2" ` -computername $strComputer foreach ($objItem in $colItems) { write-host "Availability: " $objItem.Availability write-host "Capabilities: " $objItem.Capabilities write-host "Capability Descriptions: " $objItem.CapabilityDescriptions write-host "Caption: " $objItem.Caption write-host "Configuration Manager Error Code: " $objItem.ConfigManagerErrorCode write-host "Configuration Manager User Configuration: " $objItem.ConfigManagerUserConfig write-host "Creation Class Name: " $objItem.CreationClassName write-host "Description: " $objItem.Description write-host "Device ID: " $objItem.DeviceID write-host "DMA Support: " $objItem.DMASupport write-host "Error Cleared: " $objItem.ErrorCleared write-host "Error Description: " $objItem.ErrorDescription write-host "Installation Date: " $objItem.InstallDate write-host "Last Error Code: " $objItem.LastErrorCode write-host "Maximum Number Controlled: " $objItem.MaxNumberControlled write-host "Name: " $objItem.Name write-host "Operating System Auto-Discovered: " $objItem.OSAutoDiscovered write-host "PNP DeviceID: " $objItem.PNPDeviceID write-host "Powe rManagement Capabilities: " $objItem.PowerManagementCapabilities write-host "Power Management Supported: " $objItem.PowerManagementSupported write-host "ProtocolS upported: " $objItem.ProtocolSupported write-host "Status: " $objItem.Status write-host "Status Information: " $objItem.StatusInfo write-host "System Creation Class Name: " $objItem.SystemCreationClassName write-host "System Name: " $objItem.SystemName write-host "Time Of Last Reset: " $objItem.TimeOfLastReset write-host } 

Source:Technet-Microsoft

_{(Я переписал свой предыдущий ответ, который не подходил для вашего случая.)}

Windows, по-видимому, распознает кабель, но драйвер должен был сделать более обширную эмуляцию, чтобы он был непосредственно доступен для записи.

Это заставляет вас изобретать свое собственное устройство, в данном случае универсальный принтер. Вполне возможно, что этот принтер непригоден для использования, потому что он передает контрольные коды по кабелю, на который какое-либо устройство, подключенное на другой стороне, не знает, как реагировать. В этом случае кабель принтера может быть не лучшим средством подключения устройств.

Лучшее, что я могу найти, - в статье « Получение дескриптора usbprint.sys», где была разработана программа на C для прямой записи данных на принтер в обход драйвера принтера. Вы можете использовать эту простую программу в качестве шаблона для разработки собственной программы записи данных на кабель.

Чтобы программа работала, необходимо найти GUID интерфейса в Windows кабеля, предполагая, что кабель имеет доступный GUID интерфейса. Вам нужно будет искать в реестре, используя regedit или более быстрый RegScanner .