Sometimes you need to add a generic printer in Windows 10.
Windows 10 makes the setup of newer hardware pretty automatic, but if you have a legacy or specialized printer that has to be set up as a generic printer in Windows, the process isn’t intuitive. Here’s how to set it up.
First, click in the search bar at the lower left of the screen, next to the Start button. Type “devices and printers” (without the quotes) in the bar and hit enter.
Click “Add a printer.” An option will appear that reads “Add a local printer or network printer with manual settings.” Select that and click Next.
Windows will provide a dialog box to choose your port. LPT1: is the usual choice, but pick the appropriate port if you know otherwise, such as an RS-232 serial printer. If it’s a network printer, select “Create a new port,” and choose “Standard TCP/IP port.” Click next.
Windows will ask for the manufacturer of your printer on the left. Click Generic. On the right, you’ll get a selection of drivers. Click Generic (text only), or try one of the other generic printers to see if you can get more capabilities out of the printer. If you try to print something and the first page is garbage characters, turn off the printer and cancel the print job by right-clicking on the printer icon in the system tray.
Slightly less generic printers
While you’re experimenting, you can always try some other options as well. Most printers can emulate one or more common printers from the past. The most likely choices are the Epson FX-80, Epson MX-80, HP Laserjet II, and IBM Proprinter. As a general rule, dot matrix printers emulate Epson or IBM, while inkjets and lasers emulate HP, so start there. If one of them works, you may be able to print graphics with your printer, not just text.
Further reading
If you also need to connect a network printer to Windows 10, see this entry. You can also still share Windows 10 printers by UNC, and here’s how to change your printer’s IP address if you need to.
If you’re not completely happy with Windows 10, here’s how to improve its performance.
Mounting an NFS (Network File System) share using a Unix-like operating system is pretty straight forward. But how do you mount an NFS share of a UNIX system from a Windows 10 machine? Keep reading to find out how.
NFS Only Works in Windows 10 Enterprise
Update 2012-04-20 – These instructions should now work on Windows 10 Pro (Version 10.0.14393 and above) as mentioned by EyeDocGeek in the comments.
With that said let’s install the Services for NFS feature and mount an NFS share.
Install the NFS Client (Services for NFS)
Connect To Afp From Windows 10 2017
The first thing we need to do is install the NFS Client which can be done by following the steps below:
Step 1: Open Programs and Features.
Step 2: Click Turn Windows features on or off.
Step 3: Scroll down and check the option Services for NFS, then click OK.
Step 4: Once installed, click Close and exit back to the desktop.
Enable Write Permissions for the Anonymous User
With the default options you will only have read permissions when mounting a UNIX share using the anonymous user. We can give the anonymous user write permissions by changing the UID and GID that it uses to mount the share.
The image below shows the a share mounted using the default settings.
To change the UID and GID we need to make a simple change to the Windows registry by performing the following steps:
- Open regedit by typing it in the search box end pressing Enter.
- Browse to HKEY_LOCAL_MACHINESOFTWAREMicrosoftClientForNFSCurrentVersionDefault.
- Create a new New DWORD (32-bit) Value inside the Default folder named AnonymousUid and assign the UID found on the UNIX directory as shared by the NFS system.
- Create a new New DWORD (32-bit) Value inside the Default folder named AnonymousGid and assign the GID found on the UNIX directory as shared by the NFS system.
- Restart the NFS client or reboot the machine to apply the changes.
The output of the mount command should now look like this:
Notice the 0 value applied to the UID and GID. This means the share is mounted using the root user.
How to Mount an NFS Share
Assuming your NAS device is on the same network as your Windows machine and the IP address of the device is 10.1.1.211, the following command will mount a share on the NFS system at /mnt/vms.
Firetruck LA car replacement for GTA San Andreas with automatic installation. We have the largest collection of mods for Firetruck LA car replacement for gta sa. Firetruck LA for GTA San Andreas with automatic installation. Mods are installed quickly and for free. Creator/author: BXBUGS123 Web: HTTP://YOUTUBE.COM/9BRAD0123 Downloaded: 7104x. Size: 1.6 MB Description: This is original British fire-brigade truck. Firetruck for GTA San Andreas with automatic installation. Mods are installed quickly and for free. All cars for gta san andreas with automatic installation. Steering mod adaptation. Custom settings. Pierce Arrow XT Miami Dade Fire Department Engine 45. Gta 5 lifted truck mod.
The share is now mounted and we can access the data by navigating to the Z: drive.
That’s it, we can now write to the NAS device. Although, I did notice that trying to open the share for the first time takes a long time.
We are using OSX servers and clients with AFP (Apple Filing Protocol) and want to connect the only Windows (Vista x64) client to the server shares without having to enable SMB. Is there still any AFP client for Windows available?
All that I've found are Windows AFP servers, but that's not what we need.
smorgan13.6k22 gold badges3232 silver badges4141 bronze badges
davildavil49822 gold badges55 silver badges1111 bronze badges
closed as off topic by WillMar 6 '12 at 15:23
Questions on Stack Overflow are expected to relate to programming within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here. If this question can be reworded to fit the rules in the help center, please edit the question.
1 Answer
'AFP'. That brings me back.
I'd go with SMB for the simple reason that I'd trust Apple or whoever to correctly implement SMB before I'd trust Microsoft or whoever to properly implement AFP. Not because of relative competence, but because AFP is strange, and does things in unexpected ways.
I've implemented an AFP server, so learned this the hard way.
John SaundersJohn Saunders149k2222 gold badges207207 silver badges369369 bronze badges
Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.