I've download the current version of DummyNet and according to readme I'm following these steps:
Windows: INSTALL THE NDIS DRIVER
open the configuration panel for the network card in use
(right click on the icon on the SYSTRAY, or go to
Control Panel -> Network and select one card)
click on Properties->Install->Service->Add
click on 'Driver Disk' and select 'netipfw.inf' in this folder
select 'ipfw+dummynet' which is the only service you should see
click accept on the warnings for the installation of an unknown
driver (roughly twice per existing network card)
But when I select 'netipfw.inf' and click OK the system return an error (unable to find any drivers for this device).
Note that I've previously disabled the check control for digital signature typing on Start->Exec the following command:
bcdedit /set nointegritychecks ON
and reeboting the system.
I need to be able to solve this issue because when I try to execute some dummynet command the system returns:
my_socket failed 2, cannot talk to kernel module
ipfw: socket
My network card is a NVIDIA nForce integrated on my mother board Asus Striker II.
Have you any idea to solve the problem? Thanks.
I was able to get this working using Windows 7 x64.
Download DummyNet.
Move the files from ipfw3-2012\binary64 to ipfw3-2012\binary, choose
Move and Replace
Install the driver using instruction in ipfw3-2012\binary\README.txt.
Note I had to reboot with Disable Driver Signature Enforcement as detailed
here before I could install the driver. Should look like this
Dummynet is a 32bit NDIS driver, if you look through the source at: http://info.iet.unipi.it/~luigi/dummynet you can see that the ipfw folder only has exports from ws2_32.dll
You would need to port the driver to x64 to get it to work.
Try running the command prompt as Administrator. For example, open the start menu, find command prompt, right click it and hit "run as administrator" this is likely your issue. It is similar to trying to run this on MacOS and not using the "sudo" command. If this doesn't solve your problem I would be concerned that it was because you are on 64bit and I don't believe Dummynet is compatible on that architecture yet.
Related
I'm attempting to build/install a "custom" KMDF driver (really it’s just the KMDF template in Visual Studio as is). My goal is to take a PCIe device in the device manager and update its driver to my new custom driver.
I build the KMDF template, generate an *.inf, right click and install, and I get a message saying that the operation completed.
I then go to Device Manager, right click my PCIe card, Update Driver, Browse for Drivers, Let me pick from a list, show all devices, and at this point I would expect to see "Your Manufacturer Name" in the list, but I don't. I tried changing the "ManufacturerName" in my *.inf file in Visual Studio to a unique name, but I still don't see it in the list.
Also, I'm not seeing any relevant driver information with "driverquery /V"
What do I need to do to make my custom driver appear in the list such that I can "assign" it to the hardware device?
I think the problem was that I had my configuration build set to x86 instead of x64, and I'm on an x64 machine. I changed it, and now it's working.
I am trying to get a connection to work on my machine to an AS400 database as per this link.
I have confirmed that there is no firewall blocking the machine I am working on. I have confirmed that the connection info works on a different machine with a .UDL file. I have installed the requisite C++ runtime libraries onto the machine and confirmed it has the appropriate .NET framework (it has 4.7.2). When I try to run the UDL file with the same connection information, I get "Provider cannot be found. Ensure that the provider has been installed properly." As far as I can tell I did, but it is not detecting that?
Can someone help me understand how to get it set up so that the UDL file will indicate if the connection was successful or not? I'm not really sure what is at issue at this point.
edit: I got lucky on more searching and so on further inspection, I can see that it is not in the registry editor. Could that be the issue? How would I add it there properly so that it shows up as a Data Link so that I can configure it correctly?
go here to download and install access client solutions
after installing the base package, navigate in the install folder and find the Windows_Application folder. In that folder, double click on install_acs_64.js. That will install the ODBC drivers.
run the ODBC Data Source Adminstrator app on the windows PC. Click the Add button. Select the IBM i Access ODBC Driver. Make sure to click the Server tab and set the default schema and library list.
Once the ODBC driver is installed you can test the connection by opening Excel and use the Data tab to config a connection to the IBM i database.
I installed MySQL workbench 8.0 in windows 7. After the installation I just clicked server status its through the error like Could not acquire management access for administration. Run-time Error: Unable to execute command chcp. Please make sure that the C:Windows\System32 directory is in your path environment variable. How can I solve this error?
I solved the same problem on enable the parameter "Beta : Use UTF-8 for worldwide language support" in Control Panel > Region > Administrative > Change system locale...
It's disturbing because it's have nothing about the PATH environment variable. But it's work.
Notice that I working on french environment and MySQL Workbench 8.0.24 version.
To resolve this problem on 64 bit system we have to follow two steps.
add environment variable path to C:\Windows\System32
we need chcp.com cmd file in C:\Windows\SysWOW64
copy it from C:\Windows\System32 path and paste in C:\Windows\SysWOW64
now close mysql workbench and reopen it.
Hope you got the answer.
I've reproduced the same issue by clicking server status:
Could not acquire management access for administration
RuntimeError: Unable to execute command chcp. Please make sure that the C:\Windows\System32 directory is in your PATH environment variable
and after click cancel was:
Error during ""
error calling Python module function WbAdmin.openAdminSection
using MySQL Server 8.0.23 & MySQL Workbench 8.0.23 for 64-bit OS Windows 10.
Notice: all environment variables were configured correct in my case.
Solved it only by reinstalling and using another version like MySQL Workbench 8.0.20, but I'd really recommend also downgrade version of server to MySQL Server 8.0.20 to avoid other bugs, e.g.: creating/deleting schemes and so on.
The same version should match all products to work correctly.
Found solution for system non english language users! After failing in all attempts seen issue here: Mysql Bug Forum, where told that the problem is in unicode python codec error. So mine solution as for cyrillic language user was to set Windows administrative language for the cases when utf-8 is unavailable, see screenshot below.
"System language old value was Russian, after changing to English (USA) everything started to work.
Also watched Workbench logs - there was a python exception for the ascii codec. Thats all, hope this will help.
Add the 'C:\Windows\System32' to the PATH environment variable.
Make sure you add it to PATH and not to Path.
The solution of this problem for me was this:
Start the workbench community installer after installing the program you will go to this window enter image description here then you start the option of MySQL Server the option of "Reconfigure" and you accept all the options and create a new password (if you didn't make it before), execute the final screen and you are ready to use workbench :D
Had the same error for Windows 10. For me solution was to reinstall MySQL Server 8.0.24 and to enable option in installer "Configure MySQL Server as a Windows Service". Didn't have this option marked in the first installation, so I assume the problem was in this(there were no service for it, so after system restart MySQL Workbench 8.0 CE gave an error).
As mentioned before there are 2 possible fixes:
Change system locale to English(US)
Use Workbench ver. 8.0.22 or lower (error appears on vers. 8.0.23+)
Just add the C:\Windows\System32 to the Path, and the problem will be solved!
Don't forget to add ";" to separate addresses.
I'm working on a Embedded Linux application and I would like to use GDB to debug it. The problem is that, although the Kit configuration seems fine (the Debugger option is correctly pointed to the GDB correspondent to the device's GCC - device is a Linux ARM), when I ask Qt Creator to run in debug mode it returns an error in the "Application Output":
sh: gdbserver: not found
This seems strange since, as I sad, the configuration is fine and no error about that is reported by Qt Creator in any moment before starting debug mode.
I did some research on the web to find which was the exact steps to use GDB to debug an Embedded Linux application from within Qt Creator (to use breakpoints, etc.) and the closest thing to an answer I got was this commentary by Tobias Hunger:
You will need to have ssh and gdbserver installed on your board for
this to work. Then you need to set up your board [qt-project.org] in
Creator. Afterwards you need to set up a kit [qt-project.org] using
this device.
Those steps, thought, are not clear to me.
First, why would I need to have a GDB inside the device if the Kit should point to my local GDB?
Or it shouldn't?
Where would I put the GDB anyway?
How do I know if I have this ssh on my device?
If I don't, how do I install it?
All the other mentioned steps are already done, but related to the GDB located on my Desktop Ubuntu. Should I change something if I do the above steps?
And of course, is this manual my Tobias complete or do I need to do something else for this to work?
You need gdb and ssh on your Ubuntu and gdbserver and sshd on your device: actually when you deploy a project on a remote device using QtCreator, it makes use of ssh for copying the files to target, then it launches gdbserver on the device (attached to the executable that you want to debug) and then launches gdb on your Ubuntu connecting to the running gdbserver on the device.
So you need all of them to make things working.
ssh and gdb can be installed on your Ubuntu simply via apt-get. Instead the installation of sshd and gdbserver on your board is platform-specific: it can be that some boards already have them in their standard system image, or maybe in some cases it is up to you to install them... if your Linux distribution on the board has some package manager then you might try to use it... in the worst case you will have to compile them on your own for your board and install them manually.
When I try to connect to local ports, Computer -> Connect local, using Portmon v. 3.02, I'm getting an error message, Error 2, in a small error dialog box:
I run the tool as an administrator (if not, I get error 6).
By the way this is a Windows 7 x64. On 32-bit, in Windows 7 x86, it works fine. How can I fix this problem?
Sysinternals' Portmon works only on 32-bit versions of Windows. It does not support 64-bit (probably its driver is not signed).
From the Portmon homepage:
Runs on:
Client: Windows XP (32-bit) and higher (32-bit).
Server: Windows Server 2003 (32-bit) and higher (32-bit).
In Windows Explorer, right click on portmon.exe --> select Properties --> click the Compatibility tab, and Run in Windows XP compatibility mode. It works fine like that in Windows 7 64-bit.
"Error 2" is "Cannot find the file specified", that is, cannot find a required DLL file.
Originally, you got this error when you tried to run Portmon from a network location: that broke the security trust, causing Portmon to be untrusted (or perhaps just messing up the search path somehow).
On my copy of Windows 7 64 bit, Microsoft Dependency Walker (depends.exe) tells me that PORTMSYS.SYS (the file created/loaded by Portmon.exe), has unresolved dependencies on ci.dll, clfs.sys, hal.dll and kdcom.dll.
Those are the
code integrity
common log file system
hardware abstraction layer
kernel debugger com
libraries, and they aren't actually missing: if they were, Windows wouldn't boot. However, I don't see a copy of those files in SysWow64. This suggests to me that the problem is not with portman.sys: the problem is with the win32 compatibility layer in Windows 7/64 bit: It doesn't support debug properly.
It is now 2018. There is no 64-bit version of Portmon. Serial ports are a legacy standard. The Windows 7 problem was fixed by the release of Windows 8.1. However, there is a faint chance that some Visual Studio utility or security update back-ported to Windows 7 will fix the problem. Perhaps someone who is familiar with SysWow and debugging will comment.
Instead of portmon for Windows x64, you can use an emulator of a pair of virtual COM ports and a simple program that will connect the physical port and one of the virtual ones, as well as perform the logging function.
To create a pair of virtual COM ports you can use:
com0com (preferably version "com0com-2.2.2.0-x64-fre-signed", because it contains signed x64 driver)
Virtual Serial Ports Emulator (VSPE), every time it starts on x64 it asks to purchase a driver, but it works even if you refuse.
Simple mapping and logging program can be found e.g. here or you can write it yourself, it is simple.
The sequence of actions is follows:
Сreate a pair of virtual COM ports using emulator (for example, COM28 and COM29)
Let the external device be connected to the computer COM1 port. In the program, whose exchange with external device we want to listen to, we set up a port COM28 (instead of СОМ1) for communication.
In the mapping program, we set up that we want to bind and log ports COM1 and COM29 (don't forget to set the port baud rate).
I haven't tried it yet, but this question mentions com0com. It creates two virtual serial ports and emulates a null modem cable between them. It claims to be able to run on 64 bit Windows. I'm not sure whether it comes with software that lets you just pipe input from a real port into one of the virtual ports. One of the FAQ's says that you can turn on logging.
I guess in the worst case, you could write your own small program that pipes data from a real port to one of the virtual ports and logs it all.
There's also this question on open-source alternatives that mentions a couple of projects.
I've used AccessPort
http://sudt.com/en/ap/download.htm and it works great. Very similar to Portmon
Don't start Portmon from a network drive/path or something else.
Copy on to the hard disk drive, e.g. on the desktop, restart and try again!
If you run Portmon in compatibility mode, it will work.
Check Make older programs run in this version of Windows.
It says:
To run the Program Compatibility troubleshooter:
Open the Program Compatibility troubleshooter by clicking the Start button Picture of the Start button, and then clicking Control Panel. In the search box, type troubleshooter, and then click Troubleshooting. Under Programs, click Run programs made for previous versions of Windows.
Follow the instructions in the troubleshooter.
The above is a public explanation from Microsoft for a common situation when running older applications in Windows.
But, I can say it briefly;
Right click on portmon.exe
Select menu about "troubleshooting compatibility problem" or something like that (I'm using a foreign version of Windows, so I don't see correct name of that menu in English.)
Select automatic mode
It will detect the problem and recommend Windows XP (SP2) mode
Select it and execute Portmon again.
I hope it works!
Instead of Portmon you can also use the IO Ninja program with the "Serial Monitor" plugin.
It gives a little less information than Portmon, but in a more understandable form. The main thing is, just like a Portmon, it allows you to see the data that is transmitted between a third-party application and an external device via a serial port. The program works under modern versions of Windows (I tried it myself on Windows 10 x64). The aforementioned plugin "Serial Monitor" is paid (but has an evaluation period).
Note: the port that you want to monitor must first be connected to the "IO Ninja" program, and then opened in a third-party application whose exchange with an external device you want to track.
Just to test that the hardware is working, you could perhaps boot a Linux live CD and run the statserial and/or minicom program to verify that it works. The Knoppix distribution seems to contain both those programs.
Serial ports on Linux are named /dev/ttyS0 for COM1, /dev/ttyS1 for COM2, etc.