1
1

Add to FAQ an entry about BSODs under Windows 7.

This question has come up a few times, so even though iperf3
doesn't officially support any Windows platform, I'm putting
this in here.  Thanks to @ijspzpt for the references.
Addresses #590 and possibly #546.
Этот коммит содержится в:
Bruce A. Mah 2017-10-17 10:32:19 -07:00
родитель 24da2caa09
Коммит f57d942c3a
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4984910A8CAAEE8A

Просмотреть файл

@ -93,6 +93,17 @@ I'm using the --fq-rate flag, but it does not seem to be working. Why?
I'm having trouble getting iperf3 to work on Windows, Android, etc. Where can I get help?
iperf3 only supports Linux, FreeBSD, and OSX. For other platforms we recommend using iperf2.
I managed to get a Windows executable built, but why do I get a BSOD on Windows 7?
There seems to be a bug in Windows 7 where running iperf3 from a
network filesystem can cause a system crash (in other words Blue
Screen of Death, or BSOD). This is a Windows bug addressed in kb2839149:
https://support.microsoft.com/en-us/help/2839149/stop-error-0x00000027-in-the-rdbss-sys-process-in-windows-7-or-windows
A hotfix is available under kb2732673:
https://support.microsoft.com/en-us/help/2732673/-delayed-write-failed-error-message-when--pst-files-are-stored-on-a-ne
Why cant I run a UDP client with no server?
This is potentially dangerous, and an attacker could use this for a
denial of service attack. We don't want iperf3 to be an attack tool.