Building a package using Wise Package Studio 8 to automate support for the Complex Script and East Asian language packs in Windows XP.
It worked fine the first time I tested it, but then subsequent tests unconvered an issue where any time DLLs are being replaced, I get a "Confirm File Replace" dialog I don't want.
I'm wondering if the parameters in the following script line are what's causing the Confirm File Replace to appear:

shl.Run "cmd /c start /wait rundll32 shell32,Control_RunDLL intl.cpl,,/f:""c:\intlunattend.txt"" /s:""C:\XP\I386""", 0, True

I've looked around online for more info on what the 0 and True parameters are but so far no luck. I've also tried tinkering with them on my own, running the script without them, changing the 0 to 1, etc., but haven't hit upon anything that works.

Here's the sequence of what I'm doing so far:
1. Becuse the Windows XP source files were run from a disc, long before my time as a packager, I first had to get around the prompt to insert the Windows XP source disc when trying to add language support. To solve this, I added the XP source files to my package, then editing the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SourcePath
to point to where those files are located in my package.
[font="courier new"]2. Run the script that adds the language support:

[font="times new roman"] Dim shl 
Set shl = WScript.CreateObject("WScript.Shell") 
 
Dim fso 
Set fso = WScript.CreateObject("Scripting.FileSystemObject") 

' install complex character & far east support 
'WScript.Echo "Installing Complex Script and East Asian language support"
Dim intlConfig 
Set intlConfig = fso.CreateTextFile("c:\intlunattend.txt") 

intlConfig.WriteLine "[RegionalSettings]"
intlConfig.WriteLine "LanguageGroup = 7,11" ' 7 = Japanese, 11 = Thai 
intlConfig.Close     
[font="times new roman"] shl.Run "cmd /c start /wait rundll32 shell32,Control_RunDLL intl.cpl,,/f:""c:\intlunattend.txt"" /s:""C:\XP\I386""", 136137, True
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Sorry to say this but that looks really horrid.
don't the language packs have their own EXEs you can run silently? Why use vbscript?
Answered 09/22/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
I was unaware they had their own exe's. Should these be on the XP disc? And if so, any idea what they might be named? I uncovered a few dozen exe's, some buried in CAB files, but nothing was named in a way that would lead me to think it was a language pack exe. I figured what I'd need would be in the I386\LANG folder, but I didn't see any likely candidates in there, either. Which brings up a question unrelated to my original post: what are all the files with an underbar at the end of the extension, like "PINTLCSD.DL_", for example?
Answered 09/22/2010 by: RonW
Green Belt

Please log in to comment
0
From the little I know about them, they come in EXEs or as standalone patches (MSP)
. I've never seen anything like your script needed to install them, although I confess I've had little occasion to use them
Answered 09/22/2010 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity