Windows 7 - 64 bit Loopback connector

One of the laptops I work on has no NIC (can add USB - NIC if needed), just Wifi. During the FreeAxp config, no network choice is offered up.
So on the laptop I added the loopback connector device, configured for 192.168.10.15/24, no GW, no DNS. That shows as (the only) selection as Nic for FreeAxp.
Configured TCPIP on freeaxp for 192.168.10.72/24, but no connection.
No ping, no ftp, no telnet. They can each see themself fine.

Tried on a 7-pro, and 7-home-premium both 64 bit.
Used the Microsoft provided loopback adapter.
Tried with and without pseudo MAC addres.
Try an other one? (TAP?)

A much similar config on my 32-bit XP-SP2 works fine.
Under XP the loopback connector has a 'Medium' configuration choice with I had set to Ethernet, but that choice is not volunteered under V7.
The TAP alternative for XP has an 'always connected' configuration, but the MS-loopback does not and it connects fine anyway.

I've cycles NET STOP/START MSIPCAP, and tried running FreeAxp normally and as Administrator.

Any hints?

Totaly different question... is there anything useful to do with TPS_TIMER? It indicates to be @ 1ms. Can I set it to 10ms? How?
The reason I ask is because I'd like FreeAxp to use even less CPU when idle, as riht now it is right at the fan-kick-in threshhold and I'd like to stay under that. Any knobs to turn for that?

Hein

<hr>Hein van den Heuvel
HvdH Performance Consulting
firstnamelastname.gmail.com

You running the idle loop in your configuration?

&gt;&gt; You running the idle loop in your configuration?

Yes. Otherwise it eats a full CPU right away, as to be expecgted.
It is not using much, periods of 1/2 cpu, Average less than 10%, but just enough of a tickle to exite the CPUs and make them run a little warm.

I just noticed a message about the Windows Firewall having stopped some activity. This is a fresh PC, where it was still enabled out-of-the-box. Normally I run without a firewall on windows, having all my systems behind a firewall.

For Windows-7 , is the recommendation (requirement?) to change the image property to 'run as administrator' ?

Hein


<hr>Hein van den Heuvel
HvdH Performance Consulting
firstnamelastname.gmail.com

The recommendation for all versions of Windows is to have the launch process run as administrator. it will want to poke through the firewall for WinPCAP and network support.

I have the same problem. I'm sure the software has been installed from an administartor account, and it runs as administrator.
However: looking at the properties of the looppback adaptor, I don't see MSIPCAP mentioned. All I see is:
Client for Microsoft Networks
Deterministic Network Enhancer
QoS packet Scheduler
File and Printer Sharing for Mocrosoft Networks
Internet Protocol Version 6 (TCPIP/IPV6)
Internet Protocol Version 4 (TCPIP/IPV4)
Link-Layer Topology Discovery Mapper I/O Driver
Link-Layer Topology Discovery Responder

All checked.
Sharing disabled.

IP address (alternatiive) set to match the network of the emulator`but it won't work either if it's set it fixed to the address.

Might be mising something?

From Dave Hittner:

< class='quote'>Most commercial wireless NICs “edit out” MAC addresses that are not registered to the wireless card to conserve limited wireless bandwidth, thus most emulators don’t work properly with wireless cards, as the emulators depend upon multiple MAC addresses and promiscuous mode.

The simplest thing to do is to add a wired NIC, which does not have the wireless MAC restrictions.

If you can’t add a wired NIC, the second thing to try is to set the simulated MAC address to the same as the wireless MAC address – this frequently works with TCP/IP (as long as you don’t duplicate the IP address), DECNET V (non-compatibility mode), and sometimes clustering (SCS), as the PC tends to ignore the packet protocols that it doesn’t recognize, and the IP packets which aren’t targeted to it.

DECNET IV is harder to get running with wireless, since it attempts to change the MAC address to ‘AA-00-04…’, voiding the wireless MAC connection. There is a program, SMAC, which can force the wireless MAC address to the ‘aa-00-04’ style, but it’s difficult to get Decnet IV running with this, as it complains of duplicate address on the LAN during startup – some creative circuit force down/up can occasionally fix this. LAT broadcast address can also be problematic over wireless as well - some wireless NICs pass the broadcast traffic OK, and some don’t because they edit out the unrecognized non-ip protocol to save bandwidth.

Supposedly, AirShark makes a wireless NIC which allows for full promiscuous mode implementations to allow for full wireless packet sniffing. I can’t confirm this, as I’ve never bought one.