Windows Fundamentals for Legacy PCs

The information on this page is incomplete and may not be completely accurate. I have since given up on getting dial-up to work, although reports that it can be done abound. However, I have not been able to find a simple procedure to patch an FLP install to get DUN working without a full blown (and undesirable) OS upgrade. Contributions are welcome.

See Wikipedia for more info on what this special edition of is and what it’s supposed to be for, as well as its installation method.

My interest in FLP is based in its usefulness for:

  1. Creating lean VMs to run under Fusion
  2. Creating thin clients and custom installs for several purposes (including a base environment for my portable toolkit
  3. The new generation of sub-notebooks with constrained storage space

It is, sadly, useless for real mobile use, since it lacks dial-up support (it only knows enough about modems to do TAPI and hence any form of connectivity.

Fixing the Cygwin null device

What follows are my notes on getting Cygwin to work properly on FLP, and fixing the infamous missing /dev/null device (without which you cannot get to work, and which Cygwin developers have repeatedly resisted re-implementing in another fashion).

Pretty much all of it was culled from this forum post regarding Embedded - I merely cleaned up the text a bit and confirmed it working for FLP, provided you have an Administrator account:

  1. Copy null.sys from another machine to the same location (c:\windows\system32\drivers\null.sys)
  2. Run regedit and navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\Root.
  3. Right-click on the Root folder and add the Administrator user with full control.
  4. Right-click on the Root folder again and create a new key under it called LEGACY_NULL
  5. Grab this text file and save it to your desktop
  6. Change the extension to .reg and double-click to merge with the Registry
  7. Reboot

Cygwin’s should work properly now.

Another way to verify that it is correctly installed:

  1. Go to the Start menu, right-click on My Computer and select Manage
  2. Right-click on Device Manager and select Show hidden devices from the View menu
  3. Open the Non-Plug and Play Drivers section and go to the Null driver
  4. Double-click on that device - the status panel should read This device is working properly.


Untested Procedure For Dial-Up Support

While investigating whether or not it would be possible to add dial-up support to an existing FLP install to provide HSDPA connectivity, I came across this forum post. It is apparently possible to inject the following files and registry entries from a standard install to get it to work, but I have not tested this approach.

Required Files

Filename Place in Folder
avmeter.dll C:\WINDOWS\system32
avtapi.dll C:\WINDOWS\system32
avwav.dll C:\WINDOWS\system32
communic.inf C:\WINDOWS\inf
csamsp.dll C:\WINDOWS\system32
hticons.dll C:\WINDOWS\system32
htrn_jis.dll C:\WINDOWS\system32
hypertrm.dll C:\WINDOWS\system32
hypertrm.exe C:\WINDOWS\system32
lights.exe C:\WINDOWS\system32
mdminst.dll C:\WINDOWS\system32
mdmsetup.inf C:\WINDOWS\inf
modem.sys C:\WINDOWS\system32\drivers
modemcsa.inf C:\WINDOWS\inf
modemcsa.sys C:\WINDOWS\system32\drivers
modemui.dll C:\WINDOWS\system32
rootmdm.sys C:\WINDOWS\system32\drivers
serwvdrv.dll C:\WINDOWS\system32
telephon.cpl C:\WINDOWS\system32
umdmxfrm.dll C:\WINDOWS\system32
unimdm.tsp C:\WINDOWS\system32
unimdmat.dll C:\WINDOWS\system32
uniplat.dll C:\WINDOWS\system32
usbser.sys C:\WINDOWS\system32\drivers
winchat.exe C:\WINDOWS\system32

Required Registry Entries

This page is referenced in: