Jump to content

Azureal

Valued Contributors
  • Posts

    643
  • Joined

  • Last visited

  • Days Won

    22

Everything posted by Azureal

  1. Jimmmi, This is likely possible, as long as the current chip is in a socket. A few things to consider: 1) The i7 uses more power in watts, you'll need a higher wattage power supply, higher power usage also means more heat, you need to consider whether the unit was designed to keep a faster higher power chip cool enough. 2) The BIOS must have the correct initialization microcode for the CPU you want to use, check to see if there is a similar model with the CPU you want to use, this would give you a clue as to whether the system can handle the new chip. I have successfully swapped out Core 2 Duo chips in several Dell systems, it is usually not an issue, you really MUST have the BIOS support or it will not see the chip as anything it recognizes.
  2. Jimmmi, You just need to find the correct driver, likely from Sony, to support both graphics cards. This new design paradigm allows one to run the system with the built in Intel HD graphics to save power while on battery and automatically switch to the higher performance discrete graphics system for gaming and other graphics intensive tasks. You mentioned that you wiped the drive and reinstalled Windows 7 Ultimate, you need to locate the correct grivers for both graphics systems. There may also be some other tricks to get W7 to recognize both adapters. Good luck!
  3. Another effective method of confirming the identifier for an attached USB NetMD device on Windows 7. 1) Connect the device via USB cable. 2) Watch sadly as Windows 7 fails to load a driver for the device. 3) Open the Device Manager (Right click on My Computer, select Properties, select Device Manager in upper left column). 4) Locate any "Unknown Device" entry, which likely represents the device just connected. 5) Right click on the device and click "Properties". 6) Select the "Details" tab and check the value for the property named "Hardware Ids" 7) All of the Sony NetMD devices identified to date have an id of the form "USB\VID_054C&PID_nnnn". 8) Right click on the property and select "Copy". 9) Post your results here with the name of the device and the hardware id. It seems that most of the NetMD devices manufactured have been identified, but some of the NetMD Decks may be missing or not properly identified. This is a sure fire way of identifying the device ids for every device. Once known, these devices can be added to the driver .inf file for automatic driver installation upon discovery.
  4. I think adding the USB identifiers for any Decks which are known is a great idea. I do not have any USB capable decks and cannot test any. I know there were a few driver .inf files I found the other data in which had some identifiers I did not recognize so I yanked them. I do not know if this .inf or .sys driver will work for Win32 installations, which would make the entire 32 bit section of the .inf invalid. A quick scan of the file has a readable reference to Windows 7. It may be compiled as a 64 bit library in which case it will not be loadable by any 32 bit OS version. Although your observation that the .inf references "WoW6432 i.e. 32bit hosted on 64bit" may mean you are right, it is a 32 bit driver made to work in a 64 bit environment while still retaining the ability to function as a 32 bit native driver. We can test this by trying to update a 32 bit XP install NetMD driver with this one. I'll have to check that out later. I think you are right about the issue I had with the NH600 on my machine. It was the first HiMD with a NetMD disk I tried to connect during my testing and I think it was reverting to a previously failed installation of a 32 bit NetMD driver. I had connected a couple of NetMD devices to my machine to talk to my VM install of SS, which never worked since the Windows 7 side of things would never allow connectivity. SonicStage seems to run very well on Windows 7. You'll have to test the slow upload issue and see if that is corrected. I have never used any of my RH1 units to perform transfers! Can you believe that! I just bought them because they are sweet ultimate machines...
  5. I think I'll start moving my library from my VMWare XP install over to Windows 7! We need to contact Arvin and see if we can get him to put this driver in the Ultimate installer.
  6. I updated the .inf to include as many NetMD devices as I could locate, also added as many HiMD devices and their USB codes as well. I tested with: N1 N910 RH10 NH600 All units installed without issue except the NH600, which I had to update the driver for manually in Device Manager, after which, no issues at all. Running Windows 7 Ultimate, I installed SonicStage Connect Player 4.3 Ultimate, each unit was recognized as a Net MD device in SS with an old LP2 transfer, each unit could read the disc without issue. Used the N1 to delete the old recording, ripped an album into the SS library and then transferred it to the disc as LP2. Transferred second CD of album with RH1 onto the same disc. I then proceeded to reformat the disc in the RH10 as HiMD and transferred one of the albums onto the disc as 352K ATRAC3plus. After formatting, Windows 7 reloaded the RH1 driver to see the MD unit as HiMD. Works like a charm! ; Sony Net MD ; Copyright 2010 Sony Corporation [Version] Signature="$WINDOWS NT$" Class=USB ClassGUID={36FC9E60-C465-11CF-8056-444553540000} ;CatalogFile=NETMD760.cat CatalogFile.NT=NETMD760.cat Provider=%NETMDUSB.Provider% DriverVer=05/27/2010,1.4.00.05270 [ControlFlags] ExcludeFromSelect=USB\VID_054C&PID_0075 ; MZ-N1 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_0101 ; LAM-10 ExcludeFromSelect=USB\VID_054C&PID_0113 ; AM-NX1 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 ExcludeFromSelect=USB\VID_054C&PID_0188 ; MZ-N920 ExcludeFromSelect=USB\VID_054C&PID_01E9 ; MZ-DH10P ExcludeFromSelect=USB\VID_054C&PID_0219 ; MZ-RH10 ExcludeFromSelect=USB\VID_054C&PID_021B ; MZ-RH910 ExcludeFromSelect=USB\VID_054C&PID_0286 ; MZ-RH1 [Manufacturer] %NETMDUSB.Manufacturer%=Sony,NTAMD64 ; For Win2K and later [Sony] %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0075 ; MZ-N1 %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_0101 ; LAM-10 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0113 ; AM-NX1 %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 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0188 ; MZ-N920 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_01E9 ; MZ-DH10P %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0219 ; MZ-RH10 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_021B ; MZ-RH910 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0286 ; MZ-RH1 ; For Vista 64 and Win 7 64 [Sony.NTAMD64] %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_00C7 ; MZ-N910 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0075 ; MZ-N1 %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_0101 ; LAM-10 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0113 ; AM-NX1 %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 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0188 ; MZ-N920 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_01E9 ; MZ-DH10P %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0219 ; MZ-RH10 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_021B ; MZ-RH910 %NETMDUSB.DeviceDesc%=NETMDUSB.Dev, USB\VID_054C&PID_0286 ; MZ-RH1 [SourceDisksNames] 1=%NETMDUSB.DriverDiskName%,,, [SourceDisksFiles] NETMD760.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 = NETMD760, 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\NETMD760.sys [NETMDUSB.AddReg] HKLM,%NETMDUSB.DriverGUID%,,0x00000010, HKLM,%NETMDUSB.DriverGUID%,"Name",,"Net MD Driver" HKLM,%NETMDUSB.DriverGUID%,"Version",,"1.4.00.05270" [NETMDUSB.CopyFiles] NETMD760.sys ;---------------------------------------------------------------; [Strings] NETMDUSB.Provider = "Sony Corporation" NETMDUSB.Manufacturer = "Sony Corporation" NETMDUSB.DeviceDesc = "Net MD" NETMDUSB.DriverDiskName = "Net MD Installation Disk" NETMDUSB.DriverGUID = "SOFTWARE\Wow6432Node\Sony Corporation\Net MD\{12042ff7-8d00-4384-9a25-638918b94950}" [/code]
  7. I have seen this unit come up on eBay's US site from time to time. As recently as a year ago, they were selling for 190 US dollars. I picked one up for about 135 USD within the past year. It's a great unit, awesome display! Sadly, it has not "line out" setting for the output so for driving an amplifier, it is not the best. But the fact that it uses the more common gum stick battery and has an "AA" side car, it's a perfect unit for portable use. Good luck in your search.
  8. A couple of notes: 1) The NH1 cradle does not have any USB connection at all. 2) The NH1 requires a special USB cable to connect from a standard PC/Mac USB to the NH1 unit. The cable is the same as the one (I believe) that is used for the N10 and the DH10-P Just noting this to be fair to any prospective buyers; without the special cable, you cannot transfer data to the unit ...
  9. I have looked for these in the part year and had little luck. Most of what I found were the CD style flip open case. I was not interested in that style. I found a seller on eBay who sells a lot of MD cases *tara*, she has some for sale now : MD slip cases The look like hard plastic, I never did pick any up, she was not willing to give me a break on shipping for multiple packages, the sipping costs more than the cases!
  10. Hey, no problem. I hope you can track some down. Enjoy that show ...
  11. I am on the north side of Columbus and I can spare a few HiMD blanks. If you are willing to come get them they are yours for what I paid which is six or seven bucks a piece. I have a busy weekend but I'll be available to meet you Saturday afternoon. Roger and his band as playing here in Columbus tonight, I was going to go with a friend but it didn't happen. Let me know.
  12. Azureal

    NW-HD5 malfunctioning

    Go to the menu, select "Options" then "Initialize System", then "Initialize HDD". You'll be asked to verify that you indeed want to do this two times. After a short period of time, you should be returned to the main menu. I really think that after performing this operation, you should be good to go. Let us know ... :-)
  13. Azureal

    NW-HD5 malfunctioning

    Did you perform the format disk routine, or the reset to factory defaults? I would think that performing the disk format should return the drive to its original state and prepare it for new data.
  14. Azureal

    NW-HD5 malfunctioning

    I have a couple of these units myself and they are great little players. When you say you "cleared everything off", did you use the format device option from the utility menu on the device? If you deleted the device file system contents via the USB mass storage device connection to your PC, you would likely delete required files for the unit to function properly. You can recover by performing a format device command from the utility/settings menu item. I am sorry that I don't have the exact details as I am at work and not near one of my HD5 units to verify the verbiage. Performing the format on the unit from the menu will recreate all of the necessary files for the unit to function as expected. You will need to download all of your music files via SonicStage. I believe this model also plays MP3 files without conversion and there were a couple of nice applications written over the years to make this easier to do without SS, one that comes to mind was called "Grab Your Music" or GYM, I think you can find that available here on the forums. I can verify some of this information this evening.
  15. Agreed, the movie studios are extremely paranoid. Any chance your BD player has an analog audio output? I know a couple of mine do, I have to select the analog output versus the HDMI digital output in order for sound to be output, for some reason on my players it does not output on both simultaneously. I am a little surprised that you receiver cannot decode the audio from the HDMI signal and output it onto one of its analog outputs.
  16. I think it's the headphones as well. If the unit were in Lineout mode, the volume would be fixed, you would have a terrible impedance mismatch and it would be very loud and distorted.
  17. It's definitely worth a try before laying out more cash for the box. You'll have to report back with your results.
  18. It looks like you got a pretty good deal. That unit runs off of a single AA battery, so you'll always be able to power it. I have a blue one, it is pretty light-weight and very portable. This unit is pre-NetMD so you can only record in real-time via the analog mic or optical input. Here is the unit description in the browser: R700
  19. I totally agree with Stephen, optical out of a decent deck to the optical in on a decent sound card should create a bit perfect copy of the MD and it will sound fantastic. You can pick up a decent deck for much less than an RH1 as well ...
  20. The most important factor in my opinion is to make sure you have a good impedance match between the output of your F40 and the input of the recording device. In the normal headphone output mode, it is probably in the range of 30 - 300 ohms with 250 millivolts peak to peak signal level, this will not give you a good sound when driving a line level input which expects to have 10,000 - 20,000 ohms at 1 volt peak to peak. Even cranking the volume of the F40 way up will still produce less than optimal results. If the F40 has the ability to set its output to a line level out (my R50 has a dedicated line out port) you can set that to try to get the best impedance match possible. I have several units which have a setting in the menu to toggle the headphone jack between line level and headphone level output but most of them are newer than the F40.
  21. There is something wrong with the mechanism on the site that detects new posts. This showed up as a new post for me today, 9/18/2010 at around 6PM. This is not the first time either. Old threads will show as new when selecting "View New Listings" Just a note ...
  22. Both of those E units a very sweet. I wish I had the money right now. :-/ I am certain you'll find a happy buyer.
×
×
  • Create New...