Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
I have an old PC running with MS-DOS with DX4-S CPU and base memory 640K and 256K cache.
I need to transfer all the files saved on this PC. I cannot use Floppy disks because I need thousands of them. Can I copy the files through the network? Can I use a CD driver? What would you recommend?
When your MS-DOS PC and the PC where you want to transfer the files to have a serial port you can try the following:
make a null modem cable
get a terminal emulation program for the MS-DOS PC that supports the z-modem transfer protocol
get a terminal emulation program for the PC (see link above) where you want to transfer to, that supports the z-modem transfer protocol
start both programs using the same connection settings, for example 57600 baud 8n1. When the PC is slow, decrease the baud rate on both sites
use the z-modem protocol to transfer multiple files at once
have a coffee / soda / beer / some sleep, depending on the size of the files that need transfer
ready!
MS-DOS 6.22 comes with INTERSVR.EXE and INTERLNK.EXE that allow you to transfer files over a RS-232 or parallel port.
You need a null-modem cable (RS-232) or a laplink cable (parallel port) to connect the two computers.
You run INTERSVR.EXE on your old computer.
You load INTERLNK.EXE in CONFIG.SYS on the second computer. The drives from your old computer will now be mapped to drives on your second computer and you can copy the files using a file manager of your choice.
I assume that the second computer (or a virtual machine on your second computer) will need to run DOS 6.22 or one of the DOS-based Windows versions (3.11, 95, 98, ME) for this to work.
If this installation also contains an old version of windows (3.1) and has an ethernet card, you could use that to transfer your files over.
Otherwise you could install a tcp/ip stack driver for msdos but that would be pretty hard to as you will still need a tool to actually transfer the files.
If the system also has cdrom drive you could use a bootable linux cd to transfer the files over.
If all else fails you could simply take out the hard drive and put it in another pc and copy the files like that. You might need to buy an ide to sata adapter if your other pc doesn't have ide connectors on its mainboard.
KERMIT The Kermit Project provides file transfer over RS232. Reviewing the website, it looks like Kermit is available on a variety of platforms and operating systems.
For null modem cable, you can configure KERMIT to use software handshake (XON/XOFF) and then you can hot-wire the handshake lines and just use 3 wires: TX, RX, and Signal Ground.
For example: For D25 connectors on the cable:
cross over pins 2 to 3 and 3 to 2 in the wires connecting the connectors
connect pin 7 straight through connecting wire.
tie pins 4 and 5 together on each connector but do not connect the wire
tie pins 6, 8, and 20 together on each connector but do not connect the wire
D9 connectors work the same way but have different pin assignments.
Related
I have a data buffer of data on my Serial port. This communication is developed in order to transfer the "maximum" value of possible data. Hence, the value of samples "send" if there is no connection with a computer is around ~11500 data/sec. If I attach the controller (who send the data) on a Windows 10 machine and I try to read (with java) the data, the information frequency drops down to ~ 950/1000 data/sec. Otherwise, if I attach the controller to the same machine, with the same software, but under Ubuntu, it reaches ~6000/7000 data/sec. So, there is a way to improve the Serial port under Windows?
If you are using a cheap USB-serial port, it is possible it only works at USB1 speeds, and/or the driver is basically a rebadged device driver demo from the Windows SDK (which is very poor). More expensive USB ports generally have their own drivers which are much better at higher data rates.
It is also possible that there is some sort of hardware flow control that isn't quite as efficient on Windows as it is on Linux.
Without knowing exactly which USB port you have, it's difficult to make suggestions.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am developing a USB-based peripheral device for use on Windows desktop systems and would prefer to avoid a driver installation step. In part, due to the resources required to develop and sign custom drivers, and in part as third party drivers have proved a significant stumbling block for users.
This suggests the use of a standard USB device class. HID is straightforward and flexible but has poor throughput aggrevated by MCU-specific limitations. Instead I am evaluating a scheme of impersonating a mass-storage device.
The trick being to report the metadata for a FAT filesystem containing a hidden device I/O file, which the interface application then employs raw file unbuffered I/O to communicate through. All data outside of the hard-wired I/O file sectors is reloaded into RAM at enumeration and ignored.
Thus far, this has worked surprisingly smoothly, with fast I/O and enumeration through what is presumably well-optimized path on all systems tested and no privilege elevation. However, this is clearly an abuse of the system and may fall over if Windows decides to, say, detect that the I/O data is being read back inconsistently, to defragment the cluster chain, reformat as exFAT, etc.
My question is whether such a scenario is known to occur in practice, or likely to occur in the near future? Has such a scheme been attempted the past? Will the quantity of dodgy USB mass storage devices out there form an effective shield against the operating system getting fancy?
Finally, are there any other standard USB classes or approaches which I might consider as a more reliable alternative? Windows 10 has finally added standard CDC support yet supporting earlier versions would involve bypassing signed driver installation (plus a history of BSODs, random disconnects and enumeration failures has left me wary of virtual serial devices.)
Consider using MS OS 2.0 Descriptors. Basically, you can add some special requests and descriptors to your USB device that tell Windows 8.1 and later to automatically use WinUSB for the device. Once WinUSB is installed, you can use libraries like libusb and libusbp to access the device, or just use the WinUSB API directly.
For users who are on Windows 7 or below, you could supply a signed INF-only driver, which is not too hard or expensive. See the document I wrote about it. Or you could just tell them to use a utility like Zadig to install WinUSB. Zadig gets around the driver singing requirement by inventing its own root certificate and installing it as a trusted root certificate on the user's machine.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
Improve this question
Here's the problem - I need my Bluetooth Low Energy-Only device to be able to connect to Windows 7 computers. Preferably using a regular CSR dongle, if possible. Is there any way or workaround?
I spent the two last days googling stuff to make my designer mouse working on my Lenovo T450 under Windows 7.
The solution I found may not apply to everyone: your computer must have a Bluetooth 4.0 capability (which as I understand allows Bluetooth Low Energy (aka BLE or Bluetooth Smart) to work.
The BLE drivers are not native to Windows 7 so you need to install them: go to your manufacturer's website and download the latest Intel Bluetooth drivers. Depending on the make, they might have various combinations of drivers (sometimes with overall wireless drivers, sometimes Bluetooth separately,.. I had to try about 3 - 4 different without really knowing what they meant). Once those drivers installed, you should be able to see your mouse/keyboard and pair to them.
I had to reboot my laptop multiple times and had to download a lot of different drivers from various sources but the one thing that worked was googling: Intel Bluetooth driver "your laptop make and model" and downloading the drivers.
Ps. I have also downloaded the "Microsoft Mouse and Keyboard Center" application and although opening it and trying to use it did not help at all, it might have help setting something in the background that made the drivers get installed smoothly (not an IT person, I have no idea).
I hope it helps!
Good luck
You need Bluetooth hardware that supports Bluetooth 4.0 or higher. Then just install the driver for Windows 7. Don't use Windows' internal update service (its lying and will tell you that your driver is up to date). I used this:
https://downloadcenter.intel.com/download/28510/Intel-Wireless-Bluetooth-for-Windows-7-
Well, Logitech Mx Anywhere 2 surprisingly started working with Windows 7 (Dell 380 Module on E6430 laptop) with IVT Bluesoleil Stack (unfortunately not freeware). Context menu of its icon in tray has "Bluetooth 4.0 functions", that allow adding BLE/Smart devices.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 7 years ago.
Improve this question
I am attempting to install a windows 7 SP1 32 bit virtual machine instance on my organization's openstack infrastructure. My problem is not related to setting up the .iso on Openstack, it is related to the actual windows 7 installation.
I am at the point where I can create an image with the .iso, click on 'console' and I can access windows 7's GUI as if it was on my own machine. I had no options but to "Install Windows" so I started that, but ran into problems when I get to the screen that says:
"Where do you want to install windows?"
I cannot see any disk drives to install to. Instead I see:
No drives were found. Click Load Driver to provide a mass storage
driver for installation.
I then click on 'Load Driver' and it tells me:
To install the device driver needed to access your hard drive, insert the installation media containing the driver files, and click ok. Note: the Installation media can be a floppy disk, CD, DVD, or USB flash drive.
So I click browse and I see these folders:
Computer
CD Drive (D:) GSP 1RMCPRVOL_EN_DVD
boot
efi
sources
support
upgrade
Boot (X:)
Program Files
sources
Users
Windows
From what I can see it looks like an installation CD has been baked into the ISO, but I am stuck on as to how I can use it. Whenever I select any of the folders on the D: drive, I get:
No device drivers were found. Make sure that the installation mdeia contains the correct drivers, and then click ok.
After some googling I found the location that drivers are stored on windows:
C:\Windows\System32\DriverStore
which on my system is:
X:\Windows\System32\DriverStore
And lo and behold there seems to be large list of various ones on my system. They seem to be for everything, mouse, keyboard, speakers, etc. There is about 50-100 of them, all in folders named like
.inf_x86_neutral_
I tried most of the ones that seemed to be related to the filesystem, ones like
disk
volume
etc
but none of them seem to be compatible. ("Hide drivers that are not compatible" hides them, and none of them seem to make the file system show up when I try to install them, i just get brought back to an screen with no disk drives found.)
I was just wondering if anyone knows which filesystem drivers I should look for that work for windows 7 on Openstack? Should they be on the prebaked installation CD? If so, where? Is the CD wrong?
Thanks very much.
You need VirtIO drivers. You will need to attach two devices to your volume, the iso for the OS, and the iso for these drivers. This should help
http://docs.openstack.org/image-guide/content/windows-image.html
Good luck.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 6 years ago.
Improve this question
I need two systems running, with a mic on system A going to speakers on system B, and vice versa, in realtime.
I currently have three systems set up:
Fedora
Jack works fine
Ubuntu
Jack has problems recognizing microphones
Windows
Jack works fine
I can connect Jack between the two linux systems fine, but since the ubuntu system is having jack problems regarding microphones, I'm trying to get Windows to communicate with either of them, to no avail so far. I've tried googling around but people seem to either say "It works!" or "It has problems!" without giving details.
Is there a canonical method for using netjack W<->L?
Would really appreciate any help I can get on this.
you could try jacktrip, that has an experimental windows client.
people also reported that soundjack.eu is supposed to work great, but i have never tested it (and couldn't find a linux client on their website)
I was able to get audio playback working from Windows to Linux with netjack2.
I did a small write-up of it here: https://gist.github.com/kotarou3/3813bbf7833a0e4618f7fbe8a377872d
Partially quoting here for posterity:
Stream audio from Windows to Linux
Tested on Ubuntu 16.04 and Windows 10 Redstone 1
Both boxes need to be on the same network (such that multicast packets
can be passed between them)
Installing
Linux
Setup JACK (easy to do with Cadence)
Windows
Install JACK and ASIO Bridge on the Windows
box
Run regsvr32 32bits\JackRouter.dll and regsvr32 64bits\JackRouter.dll from JACK installation directory
Modify 32bits\JackRouter.ini and 64bits\JackRouter.ini to match your channel and sample config
(Optional) Set the ASIO Bridge (Hi-Fi Audio) input as the default playback device
Running
Start the netjack2 server on Linux with jack_load netmanager (probably also possible to add to .jackdrc for it to autoload)
Run JACK NetDriver on Windows (it's in the Start menu), or jackd -R -d net
A new device named the hostname of the Windows box should have appeared on the Linux JACK patch panel
(Catia if you're
using Cadence). Connect it as you see fit (Note: Channels might not
match up as expected if you have more than 2).
Run ASIO Bridge (also in the Start menu), turn ASIO on, and set the ASIO device to JackRouter
The ASIO Bridge should have automatically set up routes to the system device in the Windows JACK patch panel. You can double check
with qjackctl (Jack Control in the Start menu) → Connections
and connect them if not
I imagine this can be further adapted to get microphone input from Windows as well by using Windows' microphone to speaker loopback feature (it's in the microphone config for Windows 10), albeit at the cost of more latency.
Basically get Windows to send the microphone to the ASIO Bridge input.