This page is a guide on how to connect your OpenDingux device to a Windows PC and what you may be able to do with such a connection. This is meant primarily for power users, and specifically those with some knowledge/experience in linux, or at least a desire to learn it, but newer users may also benefit from messing with this.

A guide for connecting from Mac or Linux can be found on the Connect from Mac or Linux page.

1. First thing: you need to set up an appropriate network driver ( here ) ( might not be needed in Windows 10). Extract the ZIP file, right click on the .inf files, and select "Install." Don't mind any errors about unsigned drivers.

2. On your PC, you may also want to download your favorite SSH and/or SFTP client if you haven't already. I generally recommend BitVise SSH, FileZilla or WinSCP. Note that FileZilla and WinSCP might not be set to show the hidden subdirectories of /media/home by default, and will have to be configured to show hidden directories in order to see them.

3. On your device, open the Network app in the Settings tab. Note the IP address if listed (it defaults to 10.1.1.2). Since this device doesn't have any WiFi, you can comfortably set this to "Allow logon without password" (unless of course you add WiFI later).

4. Connect your device via USB cable to your PC. If you're using an RG-350, use the rightmost USB port labeled USB2. Open your client of choice and configure it to connect to 10.1.1.2, username root, password leave blank. If you're a beginner, stick with using SFTP, advanced users can also open an SSH console and type Linux shell commands. FTP and Telnet are also listed, but SFTP and SSH work better respectively anyway, so I don't see much point to them.

5. When connected via SFTP, most directories will be read-only. This is normal, and is part of what makes OpenDingux relatively safe to mess with. I would like to point out a number of directories people will want to access though:
   
   
   

Location	Use
/var/log	this contains the "messages" file, which is a system log comparable to Windows Event Viewer. Handy for debugging and troubleshooting.
/proc	This contains a list of running processes, and if you're interested, a text file called "cpuinfo" which contains just what it says it does
/media	this will contain three very important subdirectories, and is the only tree you will typically be able to write to
/media/SDCARD	In the 1.5 firmware, this will be named whatever your SD card is named (rather than "SDCARD"), while in 1.7.5 or later this will always be /media/sdcard. This will be where all of the files in your external SD card are located.
/media/home	this is actually a shortcut to /media/data/local/home, but that's fine. This is where all of your configuration directories are stored for each emulator, as well as saves.
/media/data/apps	This is similar to an "Add/Remove Programs" area. To install OPK files, you put them here. To remove them, you take them out of here and put them somewhere else (I generally set aside a directory on my SD card for uninstalled OPKs).

To debug/view the output of graphical apps over ssh, launch the terminal application to disable graphical mode and run the application from the SSH terminal.