Jump to content
Sony Insider Forums


  • Content Count

  • Joined

  • Days Won


sfbp last won the day on January 25 2011

sfbp had the most liked content!

Community Reputation

8 Neutral


About sfbp

  • Rank

Profile Information

  • Gender
    Not Telling
  • Location
  • Interests
    Bridge, music, computers

Recent Profile Visitors

107,902 profile views
  1. Welcome to our forums. It takes a long time, relatively, to go through and delete duplicate posts, so please DONT DO IT. The universal drivers for 32-bit and 64 bit windows should work just fine. No idea about BeatJam, but SonicStage should do what you want.
  2. "everyone" (meaning I cannot remember and I haven't done it!) is telling me that you should be able to buy a reliable USB<->RS232 adapter for a few bucks from Amazon. I do keep my early noughties laptop (T40) for communicating with my server-monster that has a real RS232 port in the docking station. I'm sure you know all about 9pin vs 25 pin and the various aspects of RTS/CTS and flow control generally, so you will work it out - that's the most painful part I have found, even if I have got the right connection.
  3. The reason for that is that all that gets transferred back is the rights (library book checkout). NetMD cannot be transferred to PC***. Pre-RH1 limitation in USB speed (hardware/firmware). RH1 by design****. They didn't want to proliferate copies generated by NetMD transfer. For HiMD a lot less restriction because they're normal files. ***I don't think you can get anything OFF an MZ-N710 for example. ****The ability to upload MDLP bitwise built into the firmware. The ability to upload SP, if i recall correctly (and doubtless someone's gonna jump all over me with hobnailed boots) simp
  4. Not quite - M-Crew is a much better tool than SonicStage, for editing. Once USB came along, everyone was focused on the computer and transfer therefrom. No PC-Link, no accurate remote editing. You have to transfer the file somehow to the PC and edit it there.
  5. Problem solved! The R36 and R37 are clearly visible in the diagram for the MDS-S50. Maybe what happened is that they altered the 640 board enough to make the S50, then retrofitted the new board (minus a couple of zero ohm resistors at least, who knows what else!) to 640's. And why not, indeed? Where's the same spot in the JB940, I wonder? Or was that always enabled? I've never had a JB940 in my hands though a couple of times was tempted to order one from Japan - until I saw the horrendous shipping cost for something so heavy.
  6. (Chimes in with seemingly irrelevant information) Yes, and the 630 which I have proudly proclaims Type-R on the front panel. The 2656 was the main outing for Type-R ***before*** the MDLP capability was added to any device. I recall somebody claiming that the Type-R was not present in the first MDLP portables. But the R900 uses CXD-2671-203GA which surprises me if that is the case. However there's no linear progression because the CXD-2662 is the MDLP Type-R used in so many decks, and 2664 is the Type-S.
  7. BTW this is quite mysterious - that those two "jumper points" don't even exist on the schematic in the Service Manual that I have. Not that surprising I didn't know to jumper them. I definitely noticed that the board in the D5C didn't match the schematic, but that certainly would be true given that the one I recall looking at for clues was the Japanese one. I cannot begin to understand how you pieced it together! And I will be looking to see if I can work out what's going on with the D5C, too.
  8. Here is the picture you needed, which I couldn't face doing when asked (been sleeping rather badly as you have noticed this week). I see there is absolutely nothing joining R36 and R37. By absolute bad luck the flash went off in that exact spot. Today I used my new handydandy phone and it took picture without flashing anything (I guess it has a better grade of light sensor) So that's all I needed, to add a blob of solder between each of those two connection points? (forget the 0 ohm SMT resistors for this poor schmuck!)
  9. That is the sad part... we shall miss you very much indeed. Hopefully whatever it is that took you away will relent or retarget you in our direction. I'm still puzzling over what I didn't do right. And I definitely went through all the same contortions with the MXD-D5C (US/Can model) and with the same result. So will be wonderful to have that machine fully fixed and with optical output which I already added.
  10. It appears to be a bug of some sort, since if I quote a post the S for strikethrough is still there. However you should still have the HTML option to surround the text with <s>text</s>
  11. Especially since with my incompetent big thumbs I probably made an error in soldering........... waiting with bated breath
  12. Dunno if I am going to get a significant amount of sleep, up again (something to do with pollen in April I suspect). The point about the protocol used by: a. The IR controllers b. Control-A1 c. SIRCS d. PCLink Is that it is the same in all cases. This I recall being steered towards by Jim Hoggarth. One of the reasons it is so badly documented is (most likely) the variations which cause silly incompatibilities. One of the reasons that M-Crew seems a bit slow at transmitting commands is that they are sent at the speed of a person pressing buttons on a remote The only p
  13. Sounds like jiggery-pokery (hanky-panky if you prefer) to me. There are any number of scams people can and will pull with highly priced equipment. From both sides (vendor and purchaser). I never could figure out what that guy in Israel was doing with his RH1 listed at over $5000.
  14. gaaaah,,,,, no bloomin' clue, nor how to debug it either.
  15. This is from my last visit to this particular quagmire (I had blocked it out because I got exactly nowhere). I think you will find I've done the obvious connections.
  • Create New...