Running MSDE with XP Embedded

Charles Tsai

unread,

Dec 4, 2002, 11:14:44 PM12/4/02

to

Hi,

I am looking for information about running MSDE on top of

Windows XP Embedded. Would anybody kindly send

me some hints about this? Is there any possibility that

MSDE (or SQL Server) becomes one of the standard

components in XP Embedded (as SQL Server for

Windows CE does)? Any response is appreciated.

Charles

Andy Allred [MS]

unread,

Dec 5, 2002, 11:26:19 AM12/5/02

to

There will be an MSDE component "real soon now" that you can import into
your DB and add to your config. More info will be posted to the newsgroup
when it's released.

Andy

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Charles Tsai" <cha...@easyuse.com.tw> wrote in message
news:u81xVTBnCHA.2316@TK2MSFTNGP12...

Charles Tsai

unread,

Dec 5, 2002, 12:58:10 PM12/5/02

to

Thanks for your prompt response. This is good news to me ^o^

"Andy Allred [MS]" <andya...@online.microsoft.com> wrote in message
news:OuDEIsHnCHA.1392@TK2MSFTNGP10...

jpv

unread,

Dec 24, 2002, 9:23:59 AM12/24/02

to

"Andy Allred [MS]" <andya...@online.microsoft.com> wrote in message news:<OuDEIsHnCHA.1392@TK2MSFTNGP10>...

> There will be an MSDE component "real soon now" that you can import into
> your DB and add to your config. More info will be posted to the newsgroup
> when it's released.

I'm longing to have this component working. How many days do you need
to publish it ?

Thanks and happy christmas to XP Embedded team.

Andy Allred [MS]

unread,

Dec 24, 2002, 11:22:17 AM12/24/02

to

Thank you for your patience on this MSDE 'Technical Preview' package. We're
packaging it up now, i hope it'll be ready real soon, but with the holidays
already here, I'm afraid that will delay it a little. This newsgroup will be
the first place we inform about the component when it's posted to MSDN.

Andy

--
This posting is provided "AS IS" with no warranties, and confers no rights.

"jpv" <jpvasi...@infomil.com> wrote in message
news:9844c614.02122...@posting.google.com...

micro

unread,

Jan 24, 2003, 8:14:46 AM1/24/03

to

Do you really want to make a component for MSDE now or not ? I'm pushed for
time and I don't know if I have to wait for it or if I have to make it
myself.
Thanks for an answer.

"Andy Allred [MS]" <andya...@online.microsoft.com> a écrit dans le message
de news: uOuwai2qCHA.2256@TK2MSFTNGP12...

Nikolai Vorontsov

unread,

Jan 24, 2003, 8:24:41 AM1/24/03

to

Hi, Micro!

BTW, guys, you can use Windows Script Host and install MSDE during the first
startup after FBA.It's not a nice solution, but it works. I configure for
instance NetMeeting in such a way.

With WSH you can start app, and send keyboard commands to it.

--
WBR,
Nikolai Vorontsov
Quadrox NV

"micro" <ma...@infomil.com> wrote in message
news:uYtG8q6wCHA.1900@TK2MSFTNGP11...

Charles Tsai

unread,

Jan 24, 2003, 9:39:55 AM1/24/03

to

Hi, Nikolai,

Would you please kindly tell me which components do I need

to do so? And what is the size impact on the footprint

for such installation? Thanks.

Regards,

Charles

"Nikolai Vorontsov" <nic...@mail.ru> wrote in message
news:#zWKIv6wCHA.2556@TK2MSFTNGP10...

Nikolai Vorontsov

unread,

Jan 24, 2003, 10:39:39 AM1/24/03

to

Hi, Charles!

It's not a component. It's more - it's idea! :-)

Well, you need to create a component which contains:
1. MSDE installation file (if many - many files) let say in c:\temp\MSDE
directory.
2. InstallMSDE.vbs file (in the same directory).
3. Short-cut or any other mean to start InstallMSDE.vbs once after FBA.
Personally I add short-cut and after Reseal image phase manually move this
short-cut to the c:\D&S\All Users\Start Menu\Programs\Startup.

The idea is to run MSDE installation after FBA and control it automatically.

Then you have to install MSDE manually once and write down all keys you
entered.

InstallMSDE.vbs should be like this (it's mine for NetMeeting setup, I
removed all error checking for simplicity)

option explicit
dim objWsh, objFSO
set objWsh = CreateObject("WScript.Shell")
set objFSO = CreateObject("Scripting.FileSystemObject")
const CMD_DELAY = 300
const MAIN_DELAY = 3000
const RUN_DELAY = 15000

dim objExec
set objExec = objWsh.Exec("C:\Program Files\NetMeeting\Conf.exe")
WScript.Sleep MAIN_DELAY
objWsh.AppActivate "NetMeeting"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "WEBCCTV{TAB}Quadrox NV{TAB}in...@quadrox.be{TAB}WebCCTV
site{TAB}"
objWsh.SendKeys "Video surveillance system{TAB}{TAB}{ENTER}"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%L%I%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%L%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%Q%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%N"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%N{ENTER}"
WScript.Sleep RUN_DELAY
objWsh.SendKeys "%TO+{TAB}{RIGHT}%I%P{TAB}{TAB}{TAB}{ENTER}"
WScript.Sleep MAIN_DELAY
objWsh.SendKeys "%TR%N%N%O%N{ENTER}"
WScript.Sleep CMD_DELAY
objWsh.SendKeys "%CA"

to run script use something like cscript.exe InstallMSDE.vbs

This will take time each time you create a new device (during first
startup), but later device will work with MSDE.

--
WBR,
Nikolai Vorontsov
Quadrox NV

"Charles Tsai" <cha...@easyuse.com.tw> wrote in message
news:#MOYwZ7wCHA.2028@TK2MSFTNGP11...