sfbp

..... (continued). Another reason all this stuff happens has just hit me. Between Windows XP and Windows 7 (when all this stuff started going wrong) and most definitely for Windows 10, there has been a shift by Microsoft in the security settings on files stored under the individual user's ID. Things have toughened up. The default location for the .oma files is currently C:\ProgramData\SonicStage\Packages This is settable from SonicStage main menu under Tools->Options->Location to save imported files I highly recommend you move this option to somewhere where: a. you are not storing these files in a system location or under your own username b. you set the security descriptors to something that does not involve your user and does not lock out everything except Sony's programs. For example D:\SonicStage\importedfiles It's up to you of course, but simply choosing D:\SonicStage\importedfiles (if you have a hard drive at D: - modify if you don't) will do the trick. The program even gives you an option to copy the files (but see below). The other useful trick is to create a link/junction/reparse point to point to the files. I leave this to the technicians among you to implement as it's not for the beginner. It works like this: suppose you move (copy) your files onto an external drive at H:\SonicStage\importedfiles. You can make a (directory) link to this at D:\SonicStage called "importedfiles" that points to the H drive, instead of the directory "importedfiles". The beauty of this is that if your files are at X:\SonicStage\importedfiles or C:\SonicStage\importedfiles or some other place entirely, the program and database think they are still at D:\SonicStage\importedfiles. This of course saves you from having to re-add or move every music file in Sonic Stage. It also allows you to grow your library when a disk gets full (very common complaint). I don't think this is such a good idea when the storage location is C:\ProgramData\<blahblahblah>, though. Once your files are not stored under C:\ProgramData, you should have a lot less problems in Windows 7 and 10. For starters, System Restore will not mess with your files. Also anything Sony decided to make specific to your own user will not show up there, and it should be possible to change users without hassle (not sure if there is any locking of files to your user name but nothing would surprise me). This is a general observation about recent versions of Windows and your data. Finally, remember "File Conversion Tool is your friend". Files imported by most means (especially RH-1 uploads from MD) are locked to a particular installation of Windows on a particular machine. Running FCT allows you to unlock them.

One more thing I noted in your long post. Run the File Conversion Tool BEFORE you do anything else (at all) to that database. Don't be put off by the alleged time it will take (often days). Those times are for Windows 98

Ah yes, one more thing: if you descend to hacking (or cleaning) the registry, remember that SonicStage is a 32-bit application. Therefore you will have to tweak the entries in SysWOW64 rather than the main part of the registry. This could be why restore is not working, I suppose. Are you able to revive the setup up your database of music files was contained in BEFORE the SonicStage Backup? (usually the answer is: sorry, no, that machine died) If not, the answer might be to get hold of a 32-bit version of anything (XP, Vista, 7, 10) and restore to that. I know it's a nuisance but if you're really stuck (and the backup is valid) then it may work where it doesn't under 64-bit Windows. (edit) Wait a second. The copy-MACLIST.DAT fix worked? Try turning off System Restore on that drive first. Finally, a note about WAV files. Sonic Stage is rather stupid about files which it has in its database. As soon as you touch a file, SS says it's no good. So you CANNOT edit files and expect them to play without deleting them from and readding them to SS.

There is only one NetMD driver you want, and it appears you have installed it. YOU MUST GET RID OF ALL TRACES of any other NetMD driver. This means showing hidden devices and deleting them (uninstall). If you don't see any drivers at all show up (NetMD or any other devices) then you haven't turned on the ability to show them in the Windows environment variables devmgr_show_nonpresent_devices=1 devmgr_show_details=1 In addition it's important to delete ALL the relevant .INF files, including those ones that may have been copied to the hidden WINDOWS\inf directory and renamed as "oemNN.inf" where NN is an arbitrary 2 digit number. However every new device will create one of these so you should not delete ALL of them, only the ones which are for NetMD (and obviously not the NetMD760). Sorry, life is complicated. However, I don't think any of the above should be affecting your database, just the ability to connect to the device. However I am now shutting down this thread as the real problem you report probably has nothing to do with this. I merely wanted to set the record straight.

There's another possible problem IIRC. Check that you have OUR version (created by the legendary Avrin) that does not try to go to the Connect Store. Somewhere (I'll have to scrape my memory banks to figure it out) there's a URL saved that points to "Connect" that you need to get rid of. Tell us about "this restore thing". What exactly have you done, and where are your files now? Did you back them up using the Sony Tool, or simply hope that SS would be able to play them? The latter is almost certainly NOT possible unless every last one of them was "converted" (in fact decrypted) by the File Conversion Tool. Backup and Restore (Sony's) gets around that, but you have to do it right. There are people who have more experience than myself. My trick is always to put the files so that they have the same address in the database (eg K:\sonicstage\imported files\) in the new system and the old. That way you can change hard disks at least. If your problem is you cannot play back a particular file, you will have to try ffmpeg (or VLC) on it.

Same device

Absolutely not. The only other way is a deck with optical output, and then you capture it with an optical (S/PDIF) sound card. Oops, I lied. There is ONE way to get standard MD to USB, though I'm not sure of the format of the data that comes off. However there are folks who frequent here that have one. It's called an HHB Portadisc MDP-500. See here However I suspect a working one may cost you as much as an RH1. I'd stick with the RH1, since the MDP-500's transfer via USB is still limited to real time (x1).

I've already indicated the solution - a wrapper DLL which would intercept calls from the OLD gracenote API and forward them to the NEW gracenote API. Why Nielsen couldn't be bothered to do this boggles my mind. Sorry but it's beyond me, but surely there's some programmer type out there who groks the basic concept and can implement it.

I think the answer is: not at all. Most of the applications of magnetic field induction are in extremely rough environments, such as most electric motors. If it made a difference we might have a lot of failing generators, ships, planes and stoves?!?!?! One of the genius things about MD is how amazingly stable it is. The worst thing that interferes with the signal is stray light, and has to be allowed for in the calibration. I recall some disks that had different reflectivity (because the case was transparent) causing strange problems, but I don't think I've ever run into dust being responsible for a disk refusing to play. Sure, actual gunk on the head, yes, but dust - no way. Oh yes, there is one thing that I feel may interfere with MD play, which is sticky labels that get caught in the eject mechanism. Sooner or later one of these is going to catch a head (overwrite or laser) in such a way as to cripple the unit. I feel painfully aware of this when I blithely stick labels on the top and sides but there's a limit to how much you can write with felt pen on the original casing. This is my main objection to the beautiful "full metal jacket" labels which cover the disk in a seamless fashion ("seemingly seamlessly"). That, or the mechanism for ejecting and accepting the disk breaking down (belts, but also electric motors) because it has to push too hard. Stephen - whose S.O can't stand the fact that his man-cave is un-dustable!

This is a great deck. I have one FWIW. I think perhaps one of the best of all is the JB940. Try to get the Japanese one if you think you want to use the PS/2 control via PC-Link. However the playback on the 980 is Type-S, one of the few that is. Well done, anyway.

is there a CR2032 keeping state? i don't recall the circuit (and not st home now).

You can definitely get 32 bit Windows 10. It's probably Microsoft's fault if you were forcibly upgraded to 64 from 32 so you should scream loudly. I know of w7 systems that got from 32- to 32- during the free upgrade. Worst case you're going to have to pay for w10 again. Finding a 64 bit driver for your device won't be easy unless Sony has one. Sorry but i don't have time right now. Good luck. PS there may be an unsigned driver issue in W10. That we can help you with.

Ok. The regular decks don't do that. I've only ever seen the init messsage after (for example) test mode or unplugging the ribbon cable or ...? Maybe the pro decks are different. Glad you figured out to move the mechanism. I have a feeling it was the self-contradicting state it found itself in that triggered the init. YMMV. Stephen

Because it's the same subject as the other post. In any event, it wasn't removed, it was merged (if the merge didn't work correctly please accept my apologies). Merging....... BTW "Initializing" is NOT normal behaviour. It means something drastic changed in the drive and it's resetting itself.

.... which suggests that it's not due to the upgrade. You could also try booting into Safe mode, and delete the graphics driver altogether. Then you will have to find the right driver from Sony (or maybe Microsoft) and install it after you manage to boot into normal Windows. Getting into safe mode is hard but if you have access to a command line then you need to use BCDEdit. Alternatively Shift-click on "start" button when choosing the restart option should do it. Failing that, some questions: 1. Do you have an "original" install disk from Sony (perhaps W7 rather than W10 I am guessing)? 2. Are you in a position to start over with a clean install, throwing away all your data? If the answer to 2 is no, perhaps you can find a disk that will substitute for the one with all your stuff on it. This will take time and effort to replace the disk in the laptop. If you can install "original" W7 or W10 then you have your answer. If the same fault is there after the fresh install, then you also have your answer; your hardware is probably wrecked. Which brings up another point: have you got a way to upgrade the BIOS? Sounds to me like then it's time for a Sony dealer.

You (or someone else) is going to have to start by disassembling the drive properly to see what's up. From where I sit there's not much more anyone can do except that.

I think you misunderstood Microsoft's announcement, but now I understand. It's a warning (nag) that you need to get the next version of Windows by November. The update is dated June 2019, it seems (I've not dared to install it as they seem to keep going back on their implied promise to support things by taking away support for various items such as your "Vaio gate" whatever that may be). In the past, I've had a notification from MSFT that if a Windows upgrade fails or displeases in any way, that I can revert within 30 days. I'd be inclined to explore that option; and once you have that dealt with, assuming your machine is in warranty, call Sony. If it isn't in warranty, try to turn off updates and suppress these stupid (?) notifications from Microsoft. I'm not planning to upgrade beyond 1803 any time soon and I have a bunch of machines on 1703. 1709 and 1809 were both disastrous, by all accounts that I have read. Seriously though, we don't know much about VAIO. I know a lot about PC and I've never had a VAIO. This forum grew up catering to non-PC Sony devices, and the section on VAIO really doesn't provide much for anyone, sorry about that. You would be better to look in a standard PC forum.

Actually the *tuners* are. Sony engineered them cleverly so that the dependencies are in the tuner module. But with head units it's a bit of a pain because everything is packed in there.

Which is it? (not that it matters) 940 or 980? I have a nasty suspicion that you broke something when putting on the new belt. Sorry.

1. I am reasonably certain there is no November 2019 update, either now or in the future 2. This forum does not generally deal in Vaio problems, particularly Windows problems. There are many support options for you out there. 3. Please don't post twice, that is considered spamming - I deleted one post and left this one in the hope someone may have seen something like this. My only advice would be: go to safe mode and reinstall graphics drivers.

The FM transmitters for head units are REALLY HORRIBLE, in my not so humble opinion. I got an MD changer with this option and it lasted 3 weeks before I ditched it for the Unilink thing. Bluetooth, OTOH is much much better in modern cars - all one really needs. The perfect head unit (which will never be built) will be HiMD with Cell-based internet. However, if you get the NW-F88x series flash player, provided you get the Japanese version, you're good to play back ATRAC into your Bluetooth-capable headunit. And that works a treat, I have rented cars all across Europe and serenaded myself from the NW-F887 (note that the NWZ-F887 etc doesn't cut it, since it doesn't have ATRAC support). Oh yes, the other thing about radio receivers and tuner modules is that the channel spacing is different here in Amerique du Nord, 200Khz instead of 50kHz. IIRC they always had something here called side bands (esp on VHF TV which is now gone too) and so you couldn't have 105.6, 88.2 or any other such thing, only the odd ones like 105.7 and 88.1 (our two CBC radio channels still). I have a head unit in wife's car that came from HK and it's no big deal to avoid the FM "even" channels. However AM is more of a problem, the channel separation is, I think, 90 in HK (and probably elsewhere) whereas here it's 100. YMMV. It's so long since I used AM in UK that I can't recall the details. This is a real pain as you really cannot hit some local stations right on the middle of the band. I was really surprised when someone moved R4 to LW (from MW) a few years back.

You were clear, but I could only think that the reports were due to something else. Sony's stuff is reliable, but faults are often misreported Isn't VHF going the way of the dodo in Blighty?

The only variation in head units is the tuner module which is different for Europe, Asia, and N. America, and Japan. Different spacing, different bands. I don't think there's a single one that works worldwide, the exception to the general rule being some Onkyo bookshelf units, which doesn't help you. I can tell you it's possible to swap them (at least in the case of a bookshelf type unit) because I did it. Not sure how modular the car-fi is as it's a bit more crammed. The worst differences are: Japan doesn't go above 90MHz for VHF, and AM has strange bands which are sometimes 100kHz off (though it works). Could it be that you read of someone trying to use the wrong unit on European airwaves?

Probably your AIMP is not configured to call the correct (later, or latest) version of the libraries in ffmpeg, or the latest version simply isn't there. You should be able to download that. Note that VLC has its own libraries/plugins/what-have-you, it doesn't use ffmpeg directly to the best of my recollection.

Just looked at the link. Wow, impressive! Any idea what their base per-copy charge works out at (presumably includes media)?