The systems are set up to not have the NZ SSID in the connections list. For testing purposes, I also removed the normal network connection, in an attempt to force them to look for and find the HomePass relay.
I think something might have happened to the wireless card's driver somehow. When I was following your instructions, nzone locked up again (task was not scheduled), so I pressed Ctrl+C, and trying to rerun it gave me the "No compatible interface" message. When I disabled ICS, the wireless adapter disappeared from the Network Connections list completely. So I restarted the computer, and the card was showing an error in Device Manager. I uninstalled it, checked the box to delete the driver, then used the "Update Driver" option to reinstall it, and it reappeared.
>nzone start BASE16
No hosted network compatible wireless interfaces found
>nzone stop
Hosted network not started
(Ethernet connection's sharing was already disabled from before. Enabled, shared with main wireless connection. Disabled.)
>netsh wlan stop hostednetwork
The hosted network stopped.
>netsh wlan set hostednetwork disallow
The hosted network mode has been set to disallow.
>nzone start BASE16
No hosted network compatible wireless interfaces found
At this point, I've observed the following behavior:
If the hosted network is set to Disallowed, nzone will not run.
If the hosted network is set to Allowed, nzone will hang after setting it to Disallowed.
If the hosted network is set to Allowed, started with netsh, the wireless card's mac manually set, sharing enabled, then nzone will clear the mac address, set the hosted network to Disallowed, and hang.
I'm not really too worried about cycling mac addresses. If I could set it up manually, I'd be perfectly happy either changing macs manually or just leaving it on one and only getting passes once every eight hours. If I set the SSID/key for the hosted network, I can connect to it just fine, so I don't know what the difference is. The freezing behavior is new, but I'm suspecting there's something going on that isn't nzone's fault, but I'm not sure where to start tracking that down.
I'd run Maccheck before, but when I tried to run it just now so I could provide its output (in case it could be useful), it caused the entire computer to hard lock, further pointing at a problem outside of nzone. After restarting the computer, it ran without issue and gave the following output:
Broadcom,Broadcom 802.11g Network Adapter,PCI\VEN_14E4&DEV_4320&SUBSYS_70011799&REV_03\4&2B4059EA&0&28A4,BCM43XX
0000001000000001
0000000000000000000000000000000000000000000000000000000000000000
Maccheck changed the SSID to "maccheck", so I tried setting SSID/key to something so I could verify that I'm still able to connect to the hosted network and that it's being properly shared. Setting it to "Testtesttest"/"testTESTtest" allowed me to connect, have a successful connection test, and access the eShop without issues. Trying to run nzone.exe again caused it to hang, with the SSID unchanged. So the hang happens before that step.
----
Okay, new information. It hadn't been giving me any messages before, but on a whim, I disabled my antivirus again, and nzone.exe ran successfully.
>netsh wlan show hostednetwork
Hosted network settings
-----------------------
Mode : Allowed
SSID name : "ConsoleNintendo3DS"
Max number of clients : 100
Authentication : WPA2-Personal
Cipher : CCMP
Hosted network status
---------------------
Status : Started
BSSID : 4e:53:50:4f:4f:45
Radio type : 802.11g
Channel : 11
Number of clients : 1
34:af:2c:fd:5f:4a Authenticated
34:af:2c:f8:93:95 is Roommate A's 3DS, 9c:e6:35:73:88:0b is my 3DS, both of which have gotten Streetpasses just now, so I'm assuming it was Roommate B's that I caught connected. So it seems the problem has been the antivirus all along. I'm going to leave the fumbling at the start of the post intact so that if anyone else is running into the same issue, they might be able to find it.
The antivirus in question is BitDefender Free Edition. I'd previously used Avast before reinstalling windows, but after the reinstall it started popping up ads, so I had switched. I'm not familiar enough with this program yet to figure out how to add an exception so it stops blocking and causing issues with nzone.exe, but once I get that figured out, I'll post with the information. I'll also be leaving the antivirus off for a while to see how things continue to act.
Thank you again for your help, and your hard work in making this program.
Edit: I was unable to add an exclusion in BitDefender Free Antivirus. It seems the only way to do so is to have it flag a file as a virus, and then from the quarantine report, right-click the file and add it that way. Since it wasn't flagging nzone.exe itself, just blocking certain actions, it wasn't showing up in the report. With the antivirus disabled, HomePass and nzone.exe worked perfectly. I've installed AVG Free, and set an exception in it for nzone.exe, and HomePass is still working properly. Hopefully this will help anyone else who's having problems.