Usb To Rs232 Driver For Windows 10
Jackie Bullinger
When running the installer, I attempted to deselect as many install options as possible. However, selecting the serial driver automatically selected other packages, such as VISA, etc, which could not be deselected without also deselecting the driver...
Is it possible to uninstall or disable the other services and so on wihtout losing the driver functionality? As a dev machine, I try to keep the PC as clean as possible, even so there are still quite a number of services and updaters and debug servers and etc that run so keeping these to a minimum is desirable. (for PC startup time, CPU time, RAM usage, interference with other programs [eg other VISA providers], accidental interference from locally compiled programs, etc)
When you go through the installtion you can check what's going to be installed because it will have a green tick next to it. When I run through the installation procedure I can cick on VISA and select "Do not install this feature". You will be able to control what's installed through this method.
It will not allow me to deselect all features of VISA without also deselecting the NI-Serial 3.9 option. These items under VISA do not even allow the "Do not install this feature" option, as shown in the image below.
If I select do not install this feature for NI-Serial 3.9, only then can I select do not install for the entirity of VISA. But once I subsequently select install this feature for NI-Serial, the VISA features are automatically added back in.... Gah!
I note that even though I have uninstalled the NI software, NiSerU remains in my system32 drivers (am on 64-bit though?) although windows plug&play driver search fails and the device shows up as an unknown device in windows device manager.
I've looked at the NI-Serial installer and it seems that if I select the core elements that you will need the install is around 21 MB. The VISA driver is designed to be installed as the package and as individual elements that are hardware specific. 21MB shouldn't make any difference to your PC's performance and it may cause issues at a later date if the full VISA package.
Hello
My name is Paolo, from Italy, Rome.
I used the dosbox to run windows 3.11 and some other old software with full satisfaction.
The software I used are not game but some apps to control scientifics instruments and a software to draw electrical schematics.
I used DosBox as that apps are DOS Software.
That instruments comunicate to the PC by using the RS232 interface (the serial port that was a standard interface on old PC's).
There are no software update available, so, or I replace the instruments or I use a software like the DosBos to use the instruments control software.
On modern PC the serial interfaces are no more present but using a USB-to-serial converter all go OK
Using DosBox under Windows XP or Windows Vista there was no trouble.
Now, using DosBox under WIN10, the win3.11 is even wery fast until you do not activate the serial interface in the DosBox setup with the line
--> serial1=directserial realport:com5
in the DOSBox 0.74-3 Options file.
The com port is not important. COM3 or COM5 or any other is the same.
Have someone solved this issue?
Thank
Paolo
Could also be that the USB adapter itself is causing issues if it is an older one... last time we had to use a USB to RS232 adapter where I work, it took a few tries before we found one that actually functioned properly as a standard RS232 port.
On modern PC the serial interfaces are no more present but using a USB-to-serial converter all go OK
Using DosBox under Windows XP or Windows Vista there was no trouble.
Now, using DosBox under WIN10, the win3.11 is even wery fast until you do not activate the serial interface in the DosBox setup with the line
--> serial1=directserial realport:com5
in the DOSBox 0.74-3 Options file.
The com port is not important. COM3 or COM5 or any other is the same.
Thanks All for the responce
My pc is a ASUS TUF GAMING core i7 8th Gen (6 core i7).
I tryed to use DOSBOX on old pc's using win XP or win Vista without problem.
After your responce I tryed another way.
I installed DosBox under win XP using the Oracle Virtual BOX in my ASUS.
I configured XP with a com port, even using a usb to serial adapter.
Well... The Win3.11 under dos box, under win xp, under wirtual box (triple somersault!) work well, with the exclusion of the mouse that become crazy.
Therefore:
I was asking on this forum, about rs232 on dosbox, to look if someones already had my trouble and solved it.
Unfortunately, actually, I have no time to try to solve the problem.
I will use a old PC to use old software.
Thank You all
Paolo
Windows 3.11 is windows for workgroup.
Win3.11 inside the dosbox work great with the serial port ( also emulated by a usb-to serial adpter) if the main windows (where dosbox is installed) is any version up to Vista.
I also used the et_4000 win3.11 video driver to enhance screen resolution. It work well.
The only problem I have is using rs232 with win3.11, inside dosbox, inside windows10.
Tomorrow a will do some other test.
Thanks all
Paolo
Lastly, the 7/8/10 drivers might be buggy.
I used one that corrupted its own file, whenever the converter was plugged in a different USB port. Or if another converter was installed. In both situations, the driver copied a DLL or SYS file from
DRIVERS folder to SYSTEM32 folder which ended up with 0 Byte in size.
Hi,
I am using a windows 8.1 system. For flashing my spark core firmware I installed the zadig driver. Is there any way to use this driver for serial communication? The driver is listed in my device manager as USB-Device.
First I had installed the the Spark Core USB Driver according to the manual of BDub:
@Roadrunner in my case when I flash the spark I am able to see the it in the COM&LPT list, however I cannot connect to it via putty. I then press the reset and hear Windows to play a sound to indicate that a usb device has been unplugged. As soon as I hear the connect sound from Windows I connect via putty and this time it works.
For a while I thought you needed to use the spark_core.inf driver for COM and Zadig for DFU, but later I found out Zadig works for COM and DFU. EDIT: and then later I realized you really do need both! lol.
You have about 10-15 seconds before this will kick your core off the cloud, so be quick. You also have to do the above process if you want to reflash your device over the air from the web IDE, because it will be stuck in the setup() and not able to receive a new program until you connect your serial terminal properly.
I think you really do need to use the spark_core.inf driver as well but it gets along fine alongside the Zadig USB driver. We've discussed this elsewhere but I think it is useful to mention it in this post since it also has @BDubs's neat "wait while I press the key" trick.
At the moment you see the port (com3) within the device-manager, the drivers should work. (Some minutes after connecting the XGS via USB windowsupdate installs the drivers for me)
38400 is the speed i used too. After hitting the keyboard, I see something from the device.
The XG is running? You are able to ping to or through the XG?
In response to your questions:
The XG is running? You are able to ping to or through the XG?
The XG is running, its LEDs indicators are OK and we have some internal servers wich we access from the WAN through the Sophos that are currently available.
BUT... now the terminal is not regonizing the admin password (its the same I always use to log in as admin at the webadmin console). Do I have to use another password for at the console terminal? Any advice?
We just got two new XGS firewalls (delivered with 18.5.0 GA). I couldn't get a console connection on either. Upgraded to 18.5.2 and both connect fine. Also note, the actual port number may be different on your computer. Even on the same laptop, one of the XGs came up as COM3, the other XG came up as COM7.
I have an 800XL with U1MB and a built in SIO2PC board. Up until this evening I didn't know what model it was. It has a USB-B port. (I've since found out it is an Atarimax SIO2PC board. More on that later).
I read it needed the FTDI Virtual com port drivers here which I downloaded and ran the installation executable for. It looked like they were confirmed as installed, but nothing ever showed up after in device manager (ie no USB serial converter or USB serial port), even after reboots and unpluggung/plugging in the USB cable, etc, etc).
So after more reading up I managed to download the drivers separately from the FTDI website (CDM v2.12.36.4 WHQL Certified) and following the guide here on page 9 of the guide I installed the USB serial converter. I then went into the settings for the USB serial converter under device manager and enabled the "load VCP" option.
The USB serial port then appeared when I plugged and unplugged the USB cable, again with an alert indicating missing drivers. I repeated the process to manually load the drivers from the WHQL certified ones mentioned earlier.
...but powering up the Atari does nothing. It either just goers to the Basic ready prompt or, if enabled SpartaDOS-X, but I get 138 errors. Also the RespeQt activity log never does anything when I power up the Atari.
c80f0f1006