OCedHrt

Using my NW-E507..seems like the only new bitrate supported is 192kbps :/ One more is better than zero I guess.

I can confirm that Japanese and Chinese (not just Kanji) works fine in 3.2 without any registry modifications for NW-E507. MD's probably still need the registry modifications though, but I can't test how well it works since mine is dead

Isn't it the same for 2.3? Kanji works for in SS3.1 and Chinese as well if your system is configured properly. Transfering the track data to your MD would be a different problem. In that case you can only transfer Kanji. If it's the NW-E400/500 series, you can do whichever language your system is configured for. Not sure about the other Network Walkman.

Thought I should add something after getting my NW-E507. The NW-E507 actually stores the information on the player in unicode. I have been able to successfully transfer both Chinese (not just Kanji) and Japanese title/artist information with English SonicStage running in the appropriate non-unicode mode using Apploc.

That is only for Simplified to Shfit-JIS. Also that doesn't work in SS 3.x anymore. The other registry setting mentioned earlier I have confirmed to work even on Englsih SS. I swear I looked at that before when I was messing with the Jap SS. Thanks pata2001 Is the UTOC4 value still needed to get kanji to display on the unit?

I have played around with the Japanese 3.0 (might've been 3.1?) SS and couldn't get it to work right under English XP w/ non-unicode set to Japanese. I would still get a lot of ??? for the menu's and Japanese wasn't displayed everywhere. Some places worked, but not all. willykyu: SS probably calls another application to handle the transfer from PC->MD. This application is probably being called with your OS locale, and not the one set by AppLoc on SS. So you're getting a unicode->shift-jis on SS's end and it is feeding into the helper app that is doing the transfer shift-jis. Windows tries to send this shift-jis to the helper app and decodes it from french->unicode (it doesn't know it's shift-jis) and passes it to the app. That's my guess

Never had any major problem. Had a slight problem with 3.0 and 3.1 (couldn't preview clips from connect store, probably my fault). Finally completely removed OpenMG and reinstalled and it worked. But then I don't really use it much since my MD only displays NO DISC!

I have 3.1 down to 19 MB now. Seems like it is marginally smaller than 3.0. I also figured out how to install the limited patch without using the external installer, so save about 600kb there DlFileSetupJPServer.txt

Yes, showtitlehalf no longer works with SS3. It is needed, but there is more to it now. I have experimented with several combinations and the Jap version of SS3 and Windows locale set to Japanese is required. My guess is that the US version forces the latin codepage (1252) in the library. And to make it worse, the Jap version of SS3 isn't fully functional under English WinXP even with non-unicode set to Japanese.

But I have a Japanese unit That doesn't work Sigh.

The shift-jis conversion/display works fine for me under English Windows (non-unicode support set to Japanese). Works with both English or Japanese OpenMG. I do not know if the transfer to MD works though since my MD is no longer functional Some things I have discovered: *Language support of SonicStage is no longer determined by the registry. -Made copy of all registry keys made by SS/OpenMG Japanese and imported them over an English installation, and still couldn't display Japanese. *Locale setting does affect SonicStage. -Set the locale to Japanese and those ??? you see in the picture will become Japanese. This doesn't fix all the ??? though, only the ??? inside the library itself. It also fixed the shift-jis on the SS loader screen. The initialization text requires the locale to be Japanese for it to be displayed properly. I just noticed that after setting the locale to Japanese the shift-jis characters got messed up (they were entered when locale was English), but re-entering them remedies that. It then follows that changing it back to English from Japanese changes the characters to ??. My take on this is that SS uses the locale to determine which codepage conversion to use. With the Japanese locale it does a shift-jis->unicode conversion, resulting in a unicode->latin conversion that returns ??. *English SonicStage cannot import Japanese named files even when non-unicode is set to Japanese (maybe no multi-byte support?). This works fine under the Japaense version of SonicStage with non-unicode set to Japanese. I didn't try without. *You can change the checkout mode back to unlimited in the English version by changing the reg dword at HKLM\SOFTWARE\Sony Corporation\OpenMG\PD\{E1E50A82-ADC9-4263-A175-9454A6A4D7AA}\CheckoutModel to 1. The english installer sets it to 0 and the Japanese installer sets it to 1. This can be changed in the OpenMG installation script OmgCore.ini by changing the line CheckoutModel=0. (Under the English SS, from my one usage of create audio cd, I made a cd of the free "The Massacre" from connect.com and my remaining checkout count was 7. I don't know if the original was 8, or was it 7 and just didn't change.)

I believe it does say 7 but I made an audio cd with some songs from connect.com and the count didn't go down. Either that or it went from 8 to 7.

You could use a system monitor/snapshot thing to create a msi out of the ss2.3 uninstall. I wonder if that'll work...

Yep the codecs really complicate things. What has me concerned is that the wmfdist that comes with SS has mp3 decoder?/encoder? and other weird stuff too. Not too sure if they're necessary and since I have a big codec pack installed I can't really tell if missing them will have ill effects Edit: Took a look at the 9x package and found that all the codecs are the same files (figured, they're just codecs anyways) There are 3 additional files that add up to 104kb so you can really just include both together. Actaully, the inf file for Win9x is already included in the XP package of the WM9 codecs..(no idea why)..total comes to 1.07mb 7-zipped

Not too sure abuot that but I have my English WinXP set to Japanese (non-unicode programs) and the English version of SS3 still works. It wouldn't install but I just edited the ini and told it to not ignore Japanese OS. Update: Tried typing some Japanese into one of the title fields and I get jargon too. But it displays under the properties of the file.

I'm not sure if you even need shutdown.exe since the iss file has it configured to not reboot. Might be able to get away without instmsia as well... For resuming, I was talking about having the installer/script copy the downloaded zip files to the temp folder that the original SS3 installer downloads to and hoping that it will resume Not too sure if the wmf package is even needed considering that it's dated in 2002. It's based off a very early version 9 and most people would already have newer files. The WM9 Codec pack includes most of the WMV components for 1.35 MB

Well I took out most of the packages like Dx, MDAC, WMF. If you download the installer's file script you can get the links to all the components of the SS3 package. I tried to make the installer resume off those packages but doesn't work :/ Mine doesn't have dx version check, but does have msi I believe because it has the msi installer. I took out WMF because a lot of people have it as well. Could just include some info that says if you want WMA support go download it. To shave some MB off the package, run the OpenMG setup with /a. Then use the admin install in the package. You still need to include some files from the original OpenMG install but not all of them (about half? forgot). Setup.exe isn't even needed since you can just run Is_setup XD.

Try updating MDAC to the newest version. I assume that MDAC is used for the database.

2.51 is an old version. SS2.3 came with 2.8, I have no idea why the reverted back to 2.51. Also when looking thru some of the files in the 3.0 package I remember there was a typo (spelling error XD) in one of them. Forgot which one but seems like they released 3.0 in a real hurry. What does ur package include? Mine has OpenMG, MSC, the EULA, drivers, SS, and the Addon pack and is only 29->22.4mb. MDAC is about 5-6MB or ~3 with LZMA. I don't like NSIS because they won't support unicode But if overhead were a concern, you could just make a msi package..which would make it easier to maintain future versions as well. Unpacking the OpenMG package and recompressing with LZMA yields a final package of 19.8 MB

I have used inno setup and think it may also work (it also allows for 7-zip compresion of the installation packages). http://www.jrsoftware.org/isinfo.php Some things I have noticed about SS3: OpenMG is now using a MSI package, which if made properly should be able to remove/update/install itself over any previous version (since the OpenMG from 2.3 that is) MDAC included with SS3 is OLD. And I mean REALLY old. Should definitely get the newest from Microsoft if that is to be included. SS2.3 had a newer MDAC package. I have the newest one installed and it works fine. If you toss MDAC, WMF, DirectX, the package comes out to be ~22 MB 7-zipped. If you do an admin install with OpenMG and 7-zip the result, you should be able to shrink it to just under 20 MB (I didn't try, but I think it's a good guess. I did do this for my 2.3 installer). 7-zip can shrink MDAC from 5.29 to 3.5 mb (version 2.8) and I just found out sp2 for winxp comes with 2.8 SP1 which you can't obtain elsewhere.

3.0 can be had in a smaller package actually About 22 mb is enough (w/ the installer for 2.3)

Exactly. Just go to www.connect.com and click download the connect player on top. No direct linking at all, I don't see why it's so difficult The other link posted about a page back or so also links to the installer in the first post after some redirection. Seems like my installer got removed as well, didn't notice someone else had posted another one as well (only read the first page ). I can see the concern and probably shouldn't have posted it But for the adventurous, my package does work (there are some requirements). PM me if interested.

Not the setup.ini. Setup.inx file is needed to modify the data that gets added to the registry upon installation. Installshield doesn't store the registry keys in the MSI file. If you look at previous setup.inx files in a hex editor, you can easily see the registry keys like UTOC4. I can still change showtitlehalf to 1 by modifying SonicStage's configuration, but can't do it for OpenMG anymore :/

Any idea how to change the OpenMG setup.inx registry information in the SS2.3 release? The upgraded installer seems to now have it encrypted ><

Turn on multi-byte support in sonicstage. Turn on multi-byte support in the omg driver. Can als disable things like connect, burn cd, etc, I believe.