Fw 2.0 Features...


gohmifune

Still Fresh
Joined
Mar 17, 2006
Messages
30
Ok, updated the day 2.0 came out, works fine, however, the server features and such, have no idea what they are or what they do. Should I beable to connect to my computer? XP points out that there is a RDNIS device or something to that affect. Anyways, haven't seen a FAQ around, can someone point me somwhere, and/or possibly give me a quick tip or explanation?

Thanks in advance.
 
virusx posted on May 15 2006 at 05:45 AM said:
There's a good overview of all features in the new Gp2X User Guide by Guyfawkes.

We need geekier help than that. ;)

I'm trying to work on getting the Net-over-usb functionality to work with linux, but I'm running afoul of the damn hotplug system again. Such a pain in the butt...
 
Last edited by a moderator:
This is just about the most useful thing I came across with the FW 2.0: USB networking!. Let me see if I can remember how I did this(I got the info from somewhere but don't remember where:

To connect your GP2X to your windows XP via USB networking(Samba)

1. Go into the "Settings" menu and choose "System"
2. Make sure "Advanced" -> "Menu Extension" is turned ON
3. Scroll down to "USB Network" and turn it ON
4. Assign an IP (say 10.1.0.235 for example)
5. Scroll down to "Server" and turn ON "Samba Server"
6. Press B to exit saving your changes and starting up the server
7. Plug in your GP2X to your Windows computer with the USB cable: windows should start detecting a new device.
8. When Windows asks you about installing a driver tell him you will use your own (can't remember exactly how the message is but you'll know the one)
9. Copy the text below into a new file and rename the file to USBNet.inf:

;----------- begin USBNET.inf ----------------------
; MS-Windows driver config matching some basic modes of the
; Linux-USB Ethernet/RNDIS gadget firmware:
;
; - RNDIS plus CDC Ethernet ... this may be familiar as a DOCSIS
; cable modem profile, and supports most non-Microsoft USB hosts
;
; - RNDIS plus CDC Subset ... used by hardware that incapable of
; full CDC Ethernet support.
;
; Microsoft only directly supports RNDIS drivers, and bundled them into XP.
; The Microsoft "Remote NDIS USB Driver Kit" is currently found at:
; http://www.microsoft.com/whdc/hwdev/resour...ices/rndis.mspx


[Version]
Signature = "$CHICAGO$"
Class = Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %Linux%
Compatible = 1
MillenniumPreferred = .ME
DriverVer = 03/30/2004,0.0.0.0
; catalog file would be used by WHQL
;CatalogFile = Linux.cat

[Manufacturer]
%Linux% = LinuxDevices,NT.5.1

[LinuxDevices]
; NetChip IDs, used by both firmware modes
%LinuxDevice% = RNDIS, USB\VID_0525&PID_a4a2

[LinuxDevices.NT.5.1]
%LinuxDevice% = RNDIS.NT.5.1, USB\VID_0525&PID_a4a2

[ControlFlags]
ExcludeFromSelect=*

; Windows 98, Windows 98 Second Edition specific sections --------

[RNDIS]
DeviceID = usb8023
MaxInstance = 512
DriverVer = 03/30/2004,0.0.0.0
AddReg = RNDIS_AddReg_98, RNDIS_AddReg_Common

[RNDIS_AddReg_98]
HKR, , DevLoader, 0, *ndis
HKR, , DeviceVxDs, 0, usb8023.sys
HKR, NDIS, LogDriverName, 0, "usb8023"
HKR, NDIS, MajorNdisVersion, 1, 5
HKR, NDIS, MinorNdisVersion, 1, 0
HKR, Ndi\Interfaces, DefUpper, 0, "ndis3,ndis4,ndis5"
HKR, Ndi\Interfaces, DefLower, 0, "ethernet"
HKR, Ndi\Interfaces, UpperRange, 0, "ndis3,ndis4,ndis5"
HKR, Ndi\Interfaces, LowerRange, 0, "ethernet"
HKR, Ndi\Install, ndis3, 0, "RNDIS_Install_98"
HKR, Ndi\Install, ndis4, 0, "RNDIS_Install_98"
HKR, Ndi\Install, ndis5, 0, "RNDIS_Install_98"
HKR, Ndi, DeviceId, 0, "USB\VID_0525&PID_a4a2"

[RNDIS_Install_98]
CopyFiles=RNDIS_CopyFiles_98

[RNDIS_CopyFiles_98]
usb8023.sys, usb8023w.sys, , 0
rndismp.sys, rndismpw.sys, , 0

; Windows Millennium Edition specific sections --------------------

[RNDIS.ME]
DeviceID = usb8023
MaxInstance = 512
DriverVer = 03/30/2004,0.0.0.0
AddReg = RNDIS_AddReg_ME, RNDIS_AddReg_Common
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI
BusType = 15

[RNDIS_AddReg_ME]
HKR, , DevLoader, 0, *ndis
HKR, , DeviceVxDs, 0, usb8023.sys
HKR, NDIS, LogDriverName, 0, "usb8023"
HKR, NDIS, MajorNdisVersion, 1, 5
HKR, NDIS, MinorNdisVersion, 1, 0
HKR, Ndi\Interfaces, DefUpper, 0, "ndis3,ndis4,ndis5"
HKR, Ndi\Interfaces, DefLower, 0, "ethernet"
HKR, Ndi\Interfaces, UpperRange, 0, "ndis3,ndis4,ndis5"
HKR, Ndi\Interfaces, LowerRange, 0, "ethernet"
HKR, Ndi\Install, ndis3, 0, "RNDIS_Install_ME"
HKR, Ndi\Install, ndis4, 0, "RNDIS_Install_ME"
HKR, Ndi\Install, ndis5, 0, "RNDIS_Install_ME"
HKR, Ndi, DeviceId, 0, "USB\VID_0525&PID_a4a2"

[RNDIS_Install_ME]
CopyFiles=RNDIS_CopyFiles_ME

[RNDIS_CopyFiles_ME]
usb8023.sys, usb8023m.sys, , 0
rndismp.sys, rndismpm.sys, , 0

; Windows 2000 specific sections ---------------------------------

[RNDIS.NT]
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI
BusType = 15
DriverVer = 03/30/2004,0.0.0.0
AddReg = RNDIS_AddReg_NT, RNDIS_AddReg_Common
CopyFiles = RNDIS_CopyFiles_NT

[RNDIS.NT.Services]
AddService = USB_RNDIS, 2, RNDIS_ServiceInst_NT, RNDIS_EventLog

[RNDIS_CopyFiles_NT]
; no rename of files on Windows 2000, use the 'k' names as is
usb8023k.sys, , , 0
rndismpk.sys, , , 0

[RNDIS_ServiceInst_NT]
DisplayName = %ServiceDisplayName%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\usb8023k.sys
LoadOrderGroup = NDIS
AddReg = RNDIS_WMI_AddReg_NT

[RNDIS_WMI_AddReg_NT]
HKR, , MofImagePath, 0x00020000, "System32\drivers\rndismpk.sys"

; Windows XP specific sections -----------------------------------

[RNDIS.NT.5.1]
Characteristics = 0x84 ; NCF_PHYSICAL + NCF_HAS_UI
BusType = 15
DriverVer = 03/30/2004,0.0.0.0
AddReg = RNDIS_AddReg_NT, RNDIS_AddReg_Common
; no copyfiles - the files are already in place

[RNDIS.NT.5.1.Services]
AddService = USB_RNDIS, 2, RNDIS_ServiceInst_51, RNDIS_EventLog

[RNDIS_ServiceInst_51]
DisplayName = %ServiceDisplayName%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\usb8023.sys
LoadOrderGroup = NDIS
AddReg = RNDIS_WMI_AddReg_51

[RNDIS_WMI_AddReg_51]
HKR, , MofImagePath, 0x00020000, "System32\drivers\rndismp.sys"

; Windows 2000 and Windows XP common sections --------------------

[RNDIS_AddReg_NT]
HKR, Ndi, Service, 0, "USB_RNDIS"
HKR, Ndi\Interfaces, UpperRange, 0, "ndis5"
HKR, Ndi\Interfaces, LowerRange, 0, "ethernet"

[RNDIS_EventLog]
AddReg = RNDIS_EventLog_AddReg

[RNDIS_EventLog_AddReg]
HKR, , EventMessageFile, 0x00020000, "%%SystemRoot%%\System32\netevent.dll"
HKR, , TypesSupported, 0x00010001, 7

; Common Sections -------------------------------------------------

[RNDIS_AddReg_Common]
HKR, NDI\params\NetworkAddress, ParamDesc, 0, %NetworkAddress%
HKR, NDI\params\NetworkAddress, type, 0, "edit"
HKR, NDI\params\NetworkAddress, LimitText, 0, "12"
HKR, NDI\params\NetworkAddress, UpperCase, 0, "1"
HKR, NDI\params\NetworkAddress, default, 0, " "
HKR, NDI\params\NetworkAddress, optional, 0, "1"

[SourceDisksNames]
1=%SourceDisk%,,1

[SourceDisksFiles]
usb8023m.sys=1
rndismpm.sys=1
usb8023w.sys=1
rndismpw.sys=1
usb8023k.sys=1
rndismpk.sys=1

[DestinationDirs]
RNDIS_CopyFiles_98 = 10, system32/drivers
RNDIS_CopyFiles_ME = 10, system32/drivers
RNDIS_CopyFiles_NT = 12

[Strings]
ServiceDisplayName = "USB Remote NDIS Network Device Driver"
NetworkAddress = "Network Address"
Linux = "Linux Developer Community"
LinuxDevice = "Linux USB Ethernet/RNDIS Gadget"
SourceDisk = "Ethernet/RNDIS Gadget Driver Install Disk"

;----------- end USBNET.inf -----------------



10. This file is the one you will supply to Windows to give it the driver it's looking for

11. Once it finishes installing a new network connection should automatically be created. You'll need to edit this and set the IP to be in the same range as you specified for your GP2X in step 4 (for example 10.1.0.234) and set the net mask to 255.0.0.0

12. Now you just need to "look for" your GP2X from Windows Explorer by using "\\gp2x" in the address bar and you'll be able to see your GP2X as if it were another PC on the network.
 
Lobo posted on May 15 2006 at 04:56 PM said:
This is just about the most useful thing I came across with the FW 2.0: USB networking!. Let me see if I can remember how I did this(I got the info from somewhere but don't remember where:

To connect your GP2X to your windows XP via USB networking(Samba)

Now we just need to figure out how to do it in linux.


Theres so kind of wierd bug in the boars I think. It keps puting letters I typebehind the leters I justtyped?! th te dem

(Translation: There's some kind of wierd bug in the boards I think. It keeps putting letters I type behind the letters I just typed."
 
Last edited by a moderator:
Lobo posted on May 15 2006 at 10:56 PM said:
This is just about the most useful thing I came across with the FW 2.0: USB networking!. Let me see if I can remember how I did this(I got the info from somewhere but don't remember where:

To connect your GP2X to your windows XP via USB networking(Samba)

I have Windows XP SP 2 and this aborts with the specified file is not found. Of course it very helpfully does not specify WHICH file could not be found.

Can someone confirm or deny this issue?
 
Last edited by a moderator:
RiX0R posted on May 16 2006 at 01:13 PM said:
I have Windows XP SP 2 and this aborts with the specified file is not found. Of course it very helpfully does not specify WHICH file could not be found.

Can someone confirm or deny this issue?
Consider it denied. I've had it working on a workgroup based machine. The driver installed properely although I had to do it again when I reconnected the 2x the next morning.

I do have a little issue with it connecting to my Active Directory based macine though (going to post about that in a moment rather than hi-jack this thread) but the driver installed OK on there as well.
Both machines are Win XP SP2.

What XP is it you're using? I can send over the files you need if you want.
 
Last edited by a moderator:
Hey, it occurs to me...

Does USB networking require a special cable? As I understand it, standard USB can't do host-host connections with a normal cable. Maybe that's why mine isn't being detected.

Anyone have a line on this?
 
GeminiDomino posted on May 21 2006 at 11:49 AM said:
Hey, it occurs to me...

Does USB networking require a special cable? As I understand it, standard USB can't do host-host connections with a normal cable. Maybe that's why mine isn't being detected.

Anyone have a line on this?
The USB connector on the side of the 2x is a client one, not a Host USB connector. So nope, for the networking using the USB on the side requires no special cable.

If you're connecting the EXT USB part to a PC, that would have issues :)
 
Last edited by a moderator:
BenScar posted on May 21 2006 at 01:35 PM said:
GeminiDomino posted on May 21 2006 at 11:49 AM said:
Hey, it occurs to me...

Does USB networking require a special cable? As I understand it, standard USB can't do host-host connections with a normal cable. Maybe that's why mine isn't being detected.

Anyone have a line on this?
The USB connector on the side of the 2x is a client one, not a Host USB connector. So nope, for the networking using the USB on the side requires no special cable.

If you're connecting the EXT USB part to a PC, that would have issues :)

Oh, it's literally a question of the plugs. Damn it. Then Idunno why it aint working. :(

Thanks


UPDATE: Ok, so I tested it with Slax (using 2.6.x) and it just works. Plug it in, ifconfig usb0 and you're golden. So I don't know if this is an issue with my Slack installation, or with Linux 2.4.x in general.
 
Last edited by a moderator:
Back
Top