Fixed up so XP32 only needs 1 driver

[sfbp]

I just had what I hope is one of my better ideas.

Now we have established that the 64-bit driver pretty much works on all NetMD units, provided the installation file is doctored correctly, why don't we go back and fix the install files that come with the RH1 (for 32-bits) do the same?

This would mean that NetMD052.sys would work for all Net MD units. And..... no more slow down by having multiple drivers connected to USB (the "Slow SP Upload problem").

Any takers?

[sfbp]

Here's my first current shot at NETMD052.INF... those that know what they're doing can try it out. We will post a complete version in the downloads section once this is tried out and proven (for devices other than the RH1).

; Sony Net MD

; Copyright 2001,2002,2003,2004,2005 Sony Corporation


[Version]

Signature="$WINDOWS NT$"

Class=USB

ClassGUID={36FC9E60-C465-11CF-8056-444553540000}

;CatalogFile=NETMD052.cat

CatalogFile.NT=NETMD052.cat

Provider=%NETMDUSB.Provider%

DriverVer=10/31/2005,1.3.32.10310


[ControlFlags]

; NetMD Devices

ExcludeFromSelect=USB\VID_054C&PID_0075    ; MZ-N1

ExcludeFromSelect=USB\VID_054C&PID_0080    ; LAM-1

ExcludeFromSelect=USB\VID_054C&PID_0081    ; MDS-JB980

ExcludeFromSelect=USB\VID_054C&PID_0084    ; MZ-N505

ExcludeFromSelect=USB\VID_054C&PID_0085    ; MZ-S1

ExcludeFromSelect=USB\VID_054C&PID_0086    ; MZ-N707

ExcludeFromSelect=USB\VID_054C&PID_00C6    ; MZ-N10

ExcludeFromSelect=USB\VID_054C&PID_00C7    ; MZ-N910

ExcludeFromSelect=USB\VID_054C&PID_00C8    ; MZ-NF810/N710

ExcludeFromSelect=USB\VID_054C&PID_00C9    ; MZ-NF610/N510

ExcludeFromSelect=USB\VID_054C&PID_00CA    ; MZ-NE410

ExcludeFromSelect=USB\VID_054C&PID_00EB    ; MZ-NE910/NE810

ExcludeFromSelect=USB\VID_054C&PID_0188    ; MZ-N920

ExcludeFromSelect=USB\VID_054C&PID_0101    ; LAM-10

ExcludeFromSelect=USB\VID_054C&PID_0113    ; AM-NX1

; NetMD configs for HiMD Devices

ExcludeFromSelect=USB\VID_054C&PID_017E    ; MZ-NH1

ExcludeFromSelect=USB\VID_054C&PID_0180    ; MZ-NH3D

ExcludeFromSelect=USB\VID_054C&PID_0182    ; MZ-NH900

ExcludeFromSelect=USB\VID_054C&PID_0184    ; MZ-NH800/NH700

ExcludeFromSelect=USB\VID_054C&PID_0186    ; MZ-NH600/NH600D/DH710

ExcludeFromSelect=USB\VID_054C&PID_01E9    ; MZ-DH10P

ExcludeFromSelect=USB\VID_054C&PID_0219    ; MZ-RH10/M100

ExcludeFromSelect=USB\VID_054C&PID_021B    ; MZ-RH910/M10

ExcludeFromSelect=USB\VID_054C&PID_0286    ; MZ-RH1/M200 

; PC Link Devices (untested)

ExcludeFromSelect=USB\VID_054C&PID_0034    ; LINK KIT

ExcludeFromSelect=USB\VID_054C&PID_008E    ; C7NT

ExcludeFromSelect=USB\VID_054C&PID_00AD    ; L7HD

ExcludeFromSelect=USB\VID_054C&PID_00E7    ; 333NT/373NT (should be the same as each other)


[Manufacturer]

%NETMDUSB.Manufacturer%=Sony


[Sony]


; NetMD Devices

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0075    ; MZ-N1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0080    ; LAM-1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0081    ; MDS-JB980

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0084    ; MZ-N505

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0085    ; MZ-S1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0086    ; MZ-N707

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C6    ; MZ-N10

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C7    ; MZ-N910

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C8    ; MZ-NF810/N710

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C9    ; MZ-NF610/N510

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00CA    ; MZ-NE410

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00EB    ; MZ-NE910/NE810

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0188    ; MZ-N920

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0101    ; LAM-10

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0113    ; AM-NX1

; NetMD configs for HiMD Devices

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_017E    ; MZ-NH1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0180    ; MZ-NH3D

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0182    ; MZ-NH900

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0184    ; MZ-NH800/NH700

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0186    ; MZ-NH600/NH600D/DH710

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_01E9    ; MZ-DH10P

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0219    ; MZ-RH10/M100

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_021B    ; MZ-RH910/M10

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0286    ; MZ-RH1/M200

; PC Link Devices (untested, originally used pclkusb.sys)

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0034    ; LINK KIT

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_008E    ; C7NT

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00AD    ; L7HD

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00E7    ; 333NT/373NT


[SourceDisksNames]

1=%NETMDUSB.DriverDiskName%,,,


[SourceDisksFiles]

NETMD052.sys=1


[DestinationDirs]

DefaultDestDir = 10,System32\Drivers

NETMDUSB.CopyFiles = 10,System32\Drivers


[NETMDUSB.Dev.NT]

CopyFiles=NETMDUSB.CopyFiles

AddReg=NETMDUSB.AddReg


[NETMDUSB.Dev.NT.Services]

AddService = NETMD052, 0x00000002, NETMDUSB.AddService


[NETMDUSB.AddService]

DisplayName    = %NETMDUSB.DeviceDesc%

ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER

StartType      = 3                  ; SERVICE_DEMAND_START

ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL

ServiceBinary  = %10%\System32\Drivers\NETMD052.sys


[NETMDUSB.AddReg]

HKLM,%NETMDUSB.DriverGUID%,,0x00000010,

HKLM,%NETMDUSB.DriverGUID%,"Name",,"Net MD Driver"

HKLM,%NETMDUSB.DriverGUID%,"Version",,"1.3.32.10310"


[NETMDUSB.CopyFiles]

NETMD052.sys


;---------------------------------------------------------------;


[Strings]

NETMDUSB.Provider       = "Sony Corporation"

NETMDUSB.Manufacturer   = "Sony Corporation"

NETMDUSB.DeviceDesc     = "Net MD"

NETMDUSB.DriverDiskName = "Net MD Installation Disk"

NETMDUSB.DriverGUID     = "SOFTWARE\Sony Corporation\Net MD\{12042ff7-8d00-4384-9a25-638918b94950}"

[/code]


This is now (23.2.2011) updated and should work. There's still a security (unsigned driver) warning, and you may need to follow the directions below (4 posts down).

[sfbp]

Sorry to report - but I am not quite out of the woods on this one yet.

Maybe someone knows why the system keeps trying to find NETMD033.SYS even though I removed the NETMD033.INF that pointed to it.

Looks like there's some other layer getting in the way of this setup.

SIGH.

[PhilippeC]

Maybe someone knows why the system keeps trying to find NETMD033.SYS even though I removed the NETMD033.INF that pointed to it.

Looks like there's some other layer getting in the way of this setup.

As I can see with the Windows' file research tool, SonicStage or Windows created 2 files with the same name, one in the C:\Program Files\Sony\Personal Audio Driver folder and one in the C:\WINDOWS\system32\drivers folder. The *.inf file point to the ...system32\drivers why then why ...\Sony\Personal Audio Driver sys file is needed ? Perhaps there a key in the registry system that force the system to find the alternative find if any reference to NETMD033.SYS exist and ask if it is a "original" created by Windows ?

I wonder if editing this kind of file with a text editor is correct. Maybe like said a guy on the net, "You need a compiler or assembler and the source code to recreate them, or a hex editor to make small patches".

Read this : http://support.microsoft.com/kb/181345 , perhaps that will help.

[sfbp]

The installer copies the file in Personal Audio (or <wherever>) to the system32\drivers.

I agree with what you say but why does it work for the 760 driver supporting all the old units under W7? I haven't quite figured out the mechanism whereby it pulls the older drivers out when it wants to. I will read your reference on the MSFT site.

I've deleted everything relevant from windows\inf, and also from system32\drivers, to force a fresh copy, still no dice. I think it has to do with the security catalogue as I am getting the dreaded "non-certified driver" error. Even if I ignore that warning, no luck.

[sfbp]

It gets worse (the bad news). There's a copy of NETMD052.INF in C:\WINDOWS\inf (hidden directory) as OEMxx.inf, where xx is a randomly assigned (in sequence I think) decimal number of 2 digits. There's also an OEMxx.PNF file (same two digits) which gets generated during device installation, this must also be zapped.

Also it's probably necessary to delete C:\WINDOWS\inf\INFCACHE.1 but I am not certain of this.

It finally works (the good news). After numerous errors and much tweaking of the revised file (which I have posted above to replace what I posted before).

BUT NOT BEFORE ONE MORE STEP. Assuming you already deleted ALL NetMD drivers from the device map, you need to find the following key in the registry, and delete it (and also any subkeys, such as Security, and Enum) followed by a reboot of Windows. (Otherwise you will get an error, the last hurdle, saying "duplicate device name" at the end of the install which was otherwise successful).

HKLM\System\CurrentControlSet\Services\NETMDUSB

NOW IT WORKS. As there is only one driver the "Slow upload" problem for RH1 is gone forever, since it was only ever observed with 2 (or more) drivers both loaded for the same device.

There's only one fly in the ointment which some dedicated hacker-person can figure out. For some reason there is ALWAYS now the assertion that the driver is unsigned (uncertified) with a massive scary STOP message, which must be ignored. Also it generates a restore point which when done many times is a nuisance because some restore points you might want from a few weeks ago get thrown out on the Least Recently Used principle. It's also a deterrent to newbies but that won't stop the hardcore folks here.

I wish I understood why.

I need a pat on the back for this. Note that the install of multiple drivers could easily be because Sony erroneously reproduced an earlier device driver version number (1.3.30.11110) down at the bottom of NETMD052.INF, instead of the current one (1.3.32.10310) that matches the actual version of the netmd052 driver. But this may in turn be what is causing the security warning. I really don't know (yet).

PLEASE can someone who understands this stuff (I did it by guess and by golly) tell us what we have to do to avoid this security warning. I have a feeling we need to provide a new security catalog (NETMD052.CAT) but I have no clue how to do so since there is a trust certificate installed proving that the driver passed testing in Microsoft HW labs. I should be curious if this warning has been coming up under W7 for NetMD760.*, because I have not had the opportunity to try that driver under W7 myself, only relying on reports on this forum (in the other thread).

Stephen

PS. Final thought.... I recall running into the same difficulties trying to retrofit NetMD076.SYS to XP. It may well be that we can skip forward to the latest driver and there would then be only ONE for all units

[netmduser]

Do you know if this custom driver provides any improvement for netmd transfers on the netmd models? HI-MD transfers on HI-MD models seem to work faster and more reliable (even in netmd mode) ?

[sfbp]

Do you know if this custom driver provides any improvement for netmd transfers on the netmd models? HI-MD transfers on HI-MD models seem to work faster and more reliable (even in netmd mode) ?

There's no "custom" to it. All we are doing is making the more recent driver be used by ALL models.

I'm not sure I understand the second comment. A HiMD machine presents to the USB as two completely different entities:

1. A NetMD unit that understands the NetMD protocol and the NetMD formats

2. A HiMD unit that understands USB mass storage protocol (and a couple of little hidden commands from ASPI/SCSI which are used to access the hidden disk UUID).

You can hear 1 change to/from 2 by removing a legacy disk and inserting a HiMD formatted disk (either 80m or 1GB), or vice-versa. The USB "interface down" (windows) sound will be followed by the reverse "interface up" as it switches interfaces. What happens on the HiMD unit end is that the firmware disconnects from using one protocol and reconnects using the other.

Independent of all of this is the actual "raw" speed of the interface, which started getting quicker about the time HiMD was invented, and increased further when USB 2.0 was implemented for the MZ-RH1.

Clear as mud?

[netmduser]

Clear as Crystal.

I would think using the latest driver would be an improvement for netmd models.

Using a HI-MD model to make a standard MD disc just seems faster to me and more robust than a net md model. I don't know why. I didn't realize until I started using a 600D this week to make MDs.

[sfbp]

(note) This topic has nothing to do with Windows 64.

[netmduser]

(note) This topic has nothing to do with Windows 64.

will this solution work for Windows 7 32-bit? Or do you recommend 32-bit users upgrade to 64-bit (Win7)?

[sfbp]

yes it will.

you can use all the known and existing drivers with W7-32. But they will still have the "slow SP upload" nonsense.

I need to figure out WHY the security warning comes up, though. Perhaps someone can show us it doesn't happen under W7-32????

[netmduser]

I have the standard SS installation from connect.com on W7-32bit.

SonicStage : 4.3.01.14050

...

Hi-MD : 5.0.00.11280

...

Net MD : 5.0.00.11280

Do I have the latest drivers? What shows up for W7-64bit?

[sfbp]

Those are not even close to the known driver numbers for the NetMD, AFAIK. You can look in the INF I posted and cross-check, if you wish.

[Demircelik]

Here's my first current shot at NETMD052.INF... those that know what they're doing can try it out. We will post a complete version in the downloads section once this is tried out and proven (for devices other than the RH1).

; Sony Net MD

; Copyright 2001,2002,2003,2004,2005 Sony Corporation


[Version]

Signature="$WINDOWS NT{:content:}quot;

Class=USB

ClassGUID={36FC9E60-C465-11CF-8056-444553540000}

;CatalogFile=NETMD052.cat

CatalogFile.NT=NETMD052.cat

Provider=%NETMDUSB.Provider%

DriverVer=10/31/2005,1.3.32.10310


[ControlFlags]

; NetMD Devices

ExcludeFromSelect=USB\VID_054C&PID_0075    ; MZ-N1

ExcludeFromSelect=USB\VID_054C&PID_0080    ; LAM-1

ExcludeFromSelect=USB\VID_054C&PID_0081    ; MDS-JB980

ExcludeFromSelect=USB\VID_054C&PID_0084    ; MZ-N505

ExcludeFromSelect=USB\VID_054C&PID_0085    ; MZ-S1

ExcludeFromSelect=USB\VID_054C&PID_0086    ; MZ-N707

ExcludeFromSelect=USB\VID_054C&PID_00C6    ; MZ-N10

ExcludeFromSelect=USB\VID_054C&PID_00C7    ; MZ-N910

ExcludeFromSelect=USB\VID_054C&PID_00C8    ; MZ-NF810/N710

ExcludeFromSelect=USB\VID_054C&PID_00C9    ; MZ-NF610/N510

ExcludeFromSelect=USB\VID_054C&PID_00CA    ; MZ-NE410

ExcludeFromSelect=USB\VID_054C&PID_00EB    ; MZ-NE910/NE810

ExcludeFromSelect=USB\VID_054C&PID_0188    ; MZ-N920

ExcludeFromSelect=USB\VID_054C&PID_0101    ; LAM-10

ExcludeFromSelect=USB\VID_054C&PID_0113    ; AM-NX1

; NetMD configs for HiMD Devices

ExcludeFromSelect=USB\VID_054C&PID_017E    ; MZ-NH1

ExcludeFromSelect=USB\VID_054C&PID_0180    ; MZ-NH3D

ExcludeFromSelect=USB\VID_054C&PID_0182    ; MZ-NH900

ExcludeFromSelect=USB\VID_054C&PID_0184    ; MZ-NH800/NH700

ExcludeFromSelect=USB\VID_054C&PID_0186    ; MZ-NH600/NH600D/DH710

ExcludeFromSelect=USB\VID_054C&PID_01E9    ; MZ-DH10P

ExcludeFromSelect=USB\VID_054C&PID_0219    ; MZ-RH10/M100

ExcludeFromSelect=USB\VID_054C&PID_021B    ; MZ-RH910/M10

ExcludeFromSelect=USB\VID_054C&PID_0286    ; MZ-RH1/M200 

; PC Link Devices (untested)

ExcludeFromSelect=USB\VID_054C&PID_0034    ; LINK KIT

ExcludeFromSelect=USB\VID_054C&PID_008E    ; C7NT

ExcludeFromSelect=USB\VID_054C&PID_00AD    ; L7HD

ExcludeFromSelect=USB\VID_054C&PID_00E7    ; 333NT/373NT (should be the same as each other)


[Manufacturer]

%NETMDUSB.Manufacturer%=Sony


[Sony]


; NetMD Devices

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0075    ; MZ-N1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0080    ; LAM-1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0081    ; MDS-JB980

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0084    ; MZ-N505

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0085    ; MZ-S1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0086    ; MZ-N707

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C6    ; MZ-N10

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C7    ; MZ-N910

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C8    ; MZ-NF810/N710

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C9    ; MZ-NF610/N510

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00CA    ; MZ-NE410

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00EB    ; MZ-NE910/NE810

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0188    ; MZ-N920

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0101    ; LAM-10

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0113    ; AM-NX1

; NetMD configs for HiMD Devices

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_017E    ; MZ-NH1

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0180    ; MZ-NH3D

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0182    ; MZ-NH900

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0184    ; MZ-NH800/NH700

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0186    ; MZ-NH600/NH600D/DH710

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_01E9    ; MZ-DH10P

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0219    ; MZ-RH10/M100

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_021B    ; MZ-RH910/M10

%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0286    ; MZ-RH1/M200

; PC Link Devices (untested, originally used pclkusb.sys)

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0034    ; LINK KIT

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_008E    ; C7NT

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00AD    ; L7HD

;%NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00E7    ; 333NT/373NT


[SourceDisksNames]

1=%NETMDUSB.DriverDiskName%,,,


[SourceDisksFiles]

NETMD052.sys=1


[DestinationDirs]

DefaultDestDir = 10,System32\Drivers

NETMDUSB.CopyFiles = 10,System32\Drivers


[NETMDUSB.Dev.NT]

CopyFiles=NETMDUSB.CopyFiles

AddReg=NETMDUSB.AddReg


[NETMDUSB.Dev.NT.Services]

AddService = NETMD052, 0x00000002, NETMDUSB.AddService


[NETMDUSB.AddService]

DisplayName    = %NETMDUSB.DeviceDesc%

ServiceType    = 1                  ; SERVICE_KERNEL_DRIVER

StartType      = 3                  ; SERVICE_DEMAND_START

ErrorControl   = 1                  ; SERVICE_ERROR_NORMAL

ServiceBinary  = %10%\System32\Drivers\NETMD052.sys


[NETMDUSB.AddReg]

HKLM,%NETMDUSB.DriverGUID%,,0x00000010,

HKLM,%NETMDUSB.DriverGUID%,"Name",,"Net MD Driver"

HKLM,%NETMDUSB.DriverGUID%,"Version",,"1.3.32.10310"


[NETMDUSB.CopyFiles]

NETMD052.sys


;---------------------------------------------------------------;


[Strings]

NETMDUSB.Provider   	= "Sony Corporation"

NETMDUSB.Manufacturer   = "Sony Corporation"

NETMDUSB.DeviceDesc 	= "Net MD"

NETMDUSB.DriverDiskName = "Net MD Installation Disk"

NETMDUSB.DriverGUID 	= "SOFTWARE\Sony Corporation\Net MD\{12042ff7-8d00-4384-9a25-638918b94950}"

This is now (23.2.2011) updated and should work. There's still a security (unsigned driver) warning, and you may need to follow the directions below (4 posts down).

Sorry to bug you, but is it possible to download this in a file format and with instructions as to where to save it? and how to use it please?

I am looking for a solution that would work in Windows7 environment, in 32bit please.

Best regards -

[sfbp]

You do not need this for W7-32.

Just use the standard stuff and be happy.

[Demircelik]

You do not need this for W7-32.

Just use the standard stuff and be happy.

SS does not recognise NetMD (it sees HD, no problems there)

I have another machine with Win7 64bit, and, after following the advice here, I was able to get it work with both HD and NetMD formats.

So, looking for another solution, this time for 32bit please.

Best regards,

[sfbp]

You need to install the standard (XP) netMD drivers. It's possible they didn't get invoked by your 32-bit install, but if so it's a simple matter to add them. Just find the package from Sony.

You're welcome (instead) to try the (edited) NETMD052.INF - copy and paste from the above. But if you don't know how to do that, you probably won't be able to do the other steps. The only thing that my effort here does is to eliminate all drivers except NETMD052.SYS.

Not trying to be unhelpful, but if you have already made the W7-64 package work, you should know everything you need to know about messing around with these things.

[Demircelik]

You need to install the standard (XP) netMD drivers. It's possible they didn't get invoked by your 32-bit install, but if so it's a simple matter to add them. Just find the package from Sony.

You're welcome (instead) to try the (edited) NETMD052.INF - copy and paste from the above. But if you don't know how to do that, you probably won't be able to do the other steps. The only thing that my effort here does is to eliminate all drivers except NETMD052.SYS.

Not trying to be unhelpful, but if you have already made the W7-64 package work, you should know everything you need to know about messing around with these things.

Second try -

I found the three drivers from your other entry; Downloads/Drivers

titled

NetMD Driver 64-bit Win7 or Vista

so, I think, all I need is the NetMD Driver 32-bit Win7!

Hoping this will work here...

Thanks again for the excellent service...

If it means anything to anyone: when I try to install the NetMD; I get the following message (NetMD760.SYS and two other files)

Driver is not intended for this platform.

[sfbp]

Sorry for the confusion, you DO NOT want netmd760.sys

It is not designed for 32-bit systems, only for 64-bit (Vista as well as Win7, possibly even XP-64). I removed your post from the 64-bit thread as it is all getting too confusing.

What you need are the files mentioned in the above .INF file (which is netmd052.inf), netmd052.sys and netmd052.cat.

Another solution is to pretend it's not Win7 at all The only purpose of THIS thread is to allow people to install only ONE driver for W32, which seems to avoid the "slow upload" experienced by users of the MZ-RH1. If you don't have that model (or the MZ-M200 which is the same thing) you don't really care since the "slow upload" does not happen, because the RH1 is the only one which allows upload. However, if like most of us (nuts) here you have multiple kinds of units you want to connect to the USB, this fix will ensure you only install the one driver file, which (to my way of thinking) is a simpler set-up.

I'm still waiting for someone else to confirm I did it correctly, or I would have posted the driver set including this INF file as a download a while ago.

Do you have an RH1? If that's your only unit, use the drivers which got installed with it.

The regular netMD drivers are also available in the downloads section in the file pa_drivers.zip. However if you can follow this thread from the beginning, maybe you can get everything working with multiple units and ONLY the netmd052.sys driver.

Stephen

[Demircelik]

Sorry for the confusion, you DO NOT want netmd760.sys

It is not designed for 32-bit systems, only for 64-bit (Vista as well as Win7, possibly even XP-64). I removed your post from the 64-bit thread as it is all getting too confusing.

What you need are the files mentioned in the above .INF file (which is netmd052.inf), netmd052.sys and netmd052.cat.

Another solution is to pretend it's not Win7 at all The only purpose of THIS thread is to allow people to install only ONE driver for W32, which seems to avoid the "slow upload" experienced by users of the MZ-RH1. If you don't have that model (or the MZ-M200 which is the same thing) you don't really care since the "slow upload" does not happen, because the RH1 is the only one which allows upload. However, if like most of us (nuts) here you have multiple kinds of units you want to connect to the USB, this fix will ensure you only install the one driver file, which (to my way of thinking) is a simpler set-up.

I'm still waiting for someone else to confirm I did it correctly, or I would have posted the driver set including this INF file as a download a while ago.

Do you have an RH1? If that's your only unit, use the drivers which got installed with it.

The regular netMD drivers are also available in the downloads section in the file pa_drivers.zip. However if you can follow this thread from the beginning, maybe you can get everything working with multiple units and ONLY the netmd052.sys driver.

Stephen

Hi Stephen,

Thanks for trying to clear out the confusion. It seems that all that is needed are the three files you mentioned, netmd052.xxx; do you have them in your /drivers folder; or is there a convenient place I can download them without hassle?

By the way, I have found the PA_Drivers.zip file, from Sony, and downloaded it; but as I wasn't sure what it was, I did not unzip it on the W7-32 machine...

Thanks also to Sony management for making things so complicated that everyone is compelled to buy an ipod at the end!

Alex.

[sfbp]

To be fair to Sony every USB-capable unit they ever shipped worked correctly out of the box with the drivers they included with it.

You didn't answer my question: do you have an RH1?

a. if not, this whole exercise is pointless.

b. if so then you should have received drivers with it that work.

If you want to be a guinea-pig with my "single-driver" idea suggest you do that AFTER you got things working with the regular drivers.

So before we go any further: what unit(s) are you trying to support? Missing from your description is the problem you are trying to solve. It's very easy to slag off Sony when some <undefined> problem cannot be solved. Usually that's because the problem is unsolvable owing to it being undefined.

It may be time to separate this into a separate thread, the original purpose of this was not to provide a way to get users working under W7-32.

The file pa_drivers.zip DOES include the driver for the MZ-RH1 in unmodified form.

The installer in Windows 7 doesn't even need you to unzip the file, you can simply open it by pointing the installer there and navigating through until you find the driver(s) you need.

[trott3r]

Right i am confused.

I have a mzrh1 and a jb980 ans win xp pro sp3 32bit

This thread relates to rh1 users which have other minidisc units and changes the drivers so both units can be used without uninstalling the last set when switching.

Is the above correct?

Has this method not been finalised?

Since i dont see a download link to the drivers set were i would modify the .inf file.

thanks

Martin

[sfbp]

Right i am confused.

I have a mzrh1 and a jb980 ans win xp pro sp3 32bit

This thread relates to rh1 users which have other minidisc units and changes the drivers so both units can be used without uninstalling the last set when switching.

Is the above correct?

Has this method not been finalised?

Since i dont see a download link to the drivers set were i would modify the .inf file.

thanks

Martin

Yes you need this thread, Martin.

Uninstall all the drivers you can find, delete them too from the hard disk. Some are in strange places such as oem<nn>.inf.

Then install thenetmd052.sys driver using this INF file (save the contents of what I posted as NETMD052.INF, and you will also need the NETMD052.CAT file, of course). Set each and every device you want to use NetMD with to use the same driver file. You will get a <STOP> warning (unsigned driver) on every one, which you can ignore.

Let us know how you get on. I am not posting this as a complete solution until at least ONE person says they got it to work.

The test is you should be able to work with your JB980 and then switch to RH1 with no loss of upload speed on the latter. Under the "standard" regime, you will see the upload from the RH1 working at approximately x1 which is basically useless and will also wear out the unit if you use it very much (not to mention your patience!).

Stephen

[trott3r]

Yes you need this thread, Martin.

Uninstall all the drivers you can find, delete them too from the hard disk. Some are in strange places such as oem<nn>.inf.

Then install thenetmd052.sys driver using this INF file (save the contents of what I posted as NETMD052.INF, and you will also need the NETMD052.CAT file, of course). Set each and every device you want to use NetMD with to use the same driver file. You will get a <STOP> warning (unsigned driver) on every one, which you can ignore.

Let us know how you get on. I am not posting this as a complete solution until at least ONE person says they got it to work.

The test is you should be able to work with your JB980 and then switch to RH1 with no loss of upload speed on the latter. Under the "standard" regime, you will see the upload from the RH1 working at approximately x1 which is basically useless and will also wear out the unit if you use it very much (not to mention your patience!).

Stephen

Right uninstalled all netmd in usb controllers in the devicemanager.

For oemxx.inf do i do a find files for oem**.inf?

and delete what i find on the windows install?

"thenetmd052.sys"

That is in the NetMDusb.zip (old NetMD driver) i expect.

Martin

[trott3r]

-The oem.inf file i found by filesize and deleted after opening it to check its a minidisc driver.

-Deleted the netmd tree in regedit

-Copy n pasted the NETMD052.INF

-found the .sys and .cat file by searching my current xp install and copied them elsewhere.

So from what i can tell i am up to the part of reboot and install

correct?

Martin

[sfbp]

Just checking... did u uninstall all the greyed out drivers that you only see when looking at "hidden devices" after following the instructions here?

The only way to be absolutely certain about the oemxx.inf is to look at them all, sigh.

If it does NOT work, we can keep trying,,,, nothing terrible will happen.

[trott3r]

I deleted all netmd or other minidisc related drivers in device manager

under hidden devices.

I will have to manually go through all 70 odd inf files then

I might be some time....

Martin

[sfbp]

nah - windows search will look at the CONTENTS of text files, so that's a short cut of sorts.

Also if you know WHEN you started added MD support to this unit you could sort by date. And if you DO end up adding any drivers you will be able to follow where they end up.

And as I say, if it doesn't work right you can easily start again. I am actually quite keen for someone to figure out the LEAST number of steps necessary to make this work, so feel free to experiment. I'll be on hand in the incredibly unlikely event you need rescuing.

PS. if you DON'T get the <STOP> warning at driver install time, you are likely installing the old (that you don't want) drivers. So that is another clue.