![iserial serial box 2018 iserial serial box 2018](https://upload-images.jianshu.io/upload_images/20122143-3c5237ebe65e6c65.jpeg)
It won't even let me see the bios settings when putting the FreeDOS drive in. This could be, it doesn't like it at all when I swap the win10 and FreeDOS drives. Set the ports to COM5 and COM6 (I'm not sure of the addresses off the top of my head). Quick fix: Find a standalone board with jumper-configed COM ports.
#Iserial serial box 2018 driver
So unless you can find a DOS serial driver this probaly isn't going to work. Why? Win 10 probably configured the ports during startup. I wonder how HP verfied the ports via FreeDOS? Because I'm thinking on a standalone FreeDOS system you won't have access to the ports. Something just occurred to me - do those COM ports require a driver to work in FreeDOS? Or are they acutal hardware ports (vs a software-created port for use in Windows)? Is there a security config in the BIOS that protects ports/USB/etc? Maybe have a look in the BIOS first (since the port worked under Win10). I'd be tempted to disconnect anything connected to the COM ports, do a cold boot, run the same MODE commands again. (2) There's a FreeDOS TSR running that's affecting the COM ports. (A security config that prevents user access to ports?) (1) COM port config in the BIOS is wonky. BTW, The serial link was working in a Win10 cmd window prior to wiping the drive and installing FreeDOS.
#Iserial serial box 2018 install
Since its a company PC, I'd have to 'go through some hoops' to get the software that you suggest to install on this PC (haven't reached that point yet). Capslock is off.ĬF4: Thank you for the wonderful URLS. SCREENSIZE: 80 columns, 25 Rows, Mode 3, Font Height 16 LPT4 is Free for redirection to serial portsĬON codepage support (FreeDOS DISPLAY) not loaded. *** VIRTUAL PRINTER PORT 4 INFORMATION *** *** VIRTUAL PRINTER PORT 3 INFORMATION *** *** VIRTUAL PRINTER PORT 2 INFORMATION *** >mode com2 /status & baudhard=1/status response was identical except it responded with RTS auto & DTR auto. I usually have to hit 'A' twice to get the cmd line back again. No parity, 1 stop bit, 8 bit, 9600 baud, RTS on, DTR on (It is normally RTS auto, DTR auto.)Įrror reading from device com1: Write fault Use MODE COM1 BAUDHARD=1 to read * configuration* from UART It should see any bits coming across the serial connection (this scenario worked for the cmd window in win10 but not with FreeDOS as primary OS or with VMWare in Win10). My protocol analyzer is setup for 9600, 8, n, 1 on the other end of the serial cable. I can then hit the ‘A’ key twice to exit out of it. >error reading from device com1 write fault If I try writing something to the port, it fails as follows: >mode com1: baud=9600 data=8 stop=1 parity=n I see the following behavior for both com1 & com2:
#Iserial serial box 2018 manual
I tried both auto bios setup to the following standard serial settings as well as manual without success: FreeDOS serial communications would not work via VMWare in Win10 so I uninstalled Win10 and installed FreeDOS natively. It came initially with Win10 installed (HP techs verified Serial Communications via FreeDOS before purchasing).
![iserial serial box 2018 iserial serial box 2018](https://www.macsoftdownload.com/wp-content/uploads/2019/01/Serial-Box-mac.jpg)
I have not been able to establish basic RS232 Serial communications in FreeDOS on this PC.