HKLM\Software\Microsoft\Welcome

[baniaczek]

This can be valuable for ROM makers only

Bored with welcome screen? Let's play with HKLM\Software\Microsoft\Welcome

Create Key HKLM\Software\Microsoft\Welcome,
create DWORD value Disable, set some values
execute \windows\welcome.exe
and look at the screen names, which doesn't appear

• FFFF FF7F - disable everything except 'email setup' screen [WM5 only AKU 3.x]
  FFFF FFBF - disable everything except 'password' screen [WM5 only]
  FFFF FFDF - disable everything except 'complete' screen and the finishing tap
  FFFF FFEF - disable everything except 'location' screen
  FFFF FFF7 - disable everything except 'pop-up menus' screen
  FFFF FFFB - disable everything except 'stylus' screen
  FFFF FFFD - disable everything except 'align' screen
  FFFF FFFE - disable everything except tap on the first screen [ignored if any other bit is cleared, the only difference is between FFFF FFFE and FFFF FFFF]
  FFFF FFFF - disable everything [displays first 'splash' screen and exits]
  Other bits - probably reserved for the future [look at the order of the things above]

There is another value: SystemStart - I have no idea what does it mean
There is another key Software\Microsoft\Shell\Event\Welcome - I have no idea what does it mean
There are references to the files "\Storage Card\Welcome.Not" "welcome.Not" - I have no idea.

 

[vijay555]

Nice work.

V

 

[shugoh]

Great work!
Thank you.

 

[Asukal]

oh!
that is great!

i used another way to delete this entry from inflashfiles.dat and inboj.dat


Directory("\Windows\StartUp"):-File("Welcome.lnk","\Windows\welcome.lnk")

but yours better

and the others tpics,
if just replacing shellres.dll.xxx.mui on RAM
welcome will be come evry boot.

<mainly i used this for testing to make shellress.mui instantly>

i made one cab it can del the welcome.lnk from StartUP folder.
but after hard rest, welcome will come again,
(this is another topic..sorry)

 

[nottoosmart]

Ok, so i know this post is old and probably out of sight and mind. But I have an issue. This key does not exist in my registry and I only get the alignment and password setup screens. I want the whole thing enabled. Please help a brother out.

 

[luv2chill]

FYI, the welcome.not thing skips the entire wizard. We used to use this in the WM2003 days (back then you couldn't skip the stupid Dr's Appointment tutorial). It was handy if you store your touchscreen alignment in the extrom.

You just create a blank text file called welcome.not and put it on the root of your storage card (won't work in extrom, naturally). Then do a hard reset with the card inserted and it will skip the welcome wizard entirely. If you hard reset without the card inserted, the welcome wizard will proceed as normal.

However, the registry entries are far better than that method. Good find!!!

 

[trueg]

I just wanted to make a little update to this thread for anyone using this information to skip various screens during welcome.

Only the last 8 bits are actually used to select/de-select subroutines when running welcome (at least for WM 6.1).

7F - disable everything except 'email setup' screen [WM5 only AKU 3.x]
BF - disable everything except 'password' screen [WM5 only]
DF - disable everything except 'complete' screen and the finishing tap
EF - disable everything except 'location' screen
F7 - disable everything except 'pop-up menus' screen
FB - disable everything except 'stylus' screen
FD - disable everything except 'align' screen
FE - disable everything except tap on the first screen
FF - disable everything [displays first 'splash' screen and exits]

For my ROM, I wanted to run welcome with align, location & complete screen.

1111 1101 (FD) - align screen
1110 1111 (EF) - location screen
1101 1111 (DF) - complete screen
---------------
1100 1101 (CD) or 205

ends up being....

<wap-provisioningdoc>
  <!--334.05_Welcome-->
  <characteristic type="Registry">
    <characteristic type="HKLM\Software\Microsoft\Welcome">
      <parm name="Disable" datatype="integer" value="205" />
    </characteristic>
  </characteristic>
</wap-provisioningdoc>

 

[irus]

also if you want to skip everying just put the file welcome.not in the root of the storage card. **.not is the file extension **

 

[trueg]

also if you want to skip everying just put the file welcome.not in the root of the storage card. **.not is the file extension **

Yes indeed, but make sure you apply the alignment settings by another means (provxml, cab, etc). I just spent a few days trying to figure out why endkey.exe was not working in the most recent version of my ROM (I use it to switch between vibrate/ring on long end key press). Turns out that if you don't do the align and you don't apply the settings some other way, endkey.exe does not work when you do a long press of the end key (at least on my Touch Pro).

 

[adwinp]

I'm reviving this old thread since I'm running into an issue.
I usually disable everything in my ROM, thus:
Disable=dword:ff (or ffffffff)

After customization though, I need to tap on the taskbar to lauch the home screen. Otherwise, it just stays on the welcome splash.

Any ideas?

 

[chrisd1a1]

just bumping this up as i'd really appreciate an assist.

i've been trying to change the first boot in my 6.5.x build rom.

all i want is the 'allign screen' working

the current entry is

[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
"Disable" = dword:00000080

i may be thick but i'm really having trouble getting my head round this. i've tried

"Disable" = dword:FD
"Disable" = dword:1111 1101
"Disable" = dword:FFFF FFFD

which are all from this thread but none of these are working.

does anyone know what the entry actually is for 6.5.x? and if so i'd be grateful if someone could help.

many thanks in advance

Chris

 

[RoryB]

I use

[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
; only doing screen calibrate
  "Disable"=dword:fffffffc

 

[chrisd1a1]

I use

[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
; only doing screen calibrate
  "Disable"=dword:fffffffc

cheers for that. will give it a try when i get home

 

[chrisd1a1]

I use

[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
  "Disable"=dword:fffffffc

i must be doing something wrong.. no matter what i try it's not changing the boot setup

it's still going 'tap', 'calibrate', 'time/date', and 'password'....

all i want is Tap and calibrate!!!!

this is doing my head in. i'd appreciate any other ideas???

many thanks to anyone who may be able to help

Chris

 

[cruiserrr]

I will try to explain how to get any number you need:

1. Put this table in an excel,
2. Find the 8 digits corresponding to EACH of the screens wanted (eg. tap screen is FD or 253 and align screen is FE or 254 )
3. Tap each digit in a column (one line per screen wanted)
4. calculate the minimum of each column and get the 8 digits (in the example, min of 11111101 and 11111110 is 11111100).
5. If you use provxml go the other way round and with the total calculated find the Dec Value (3rd column) corresponding to the 8 digits (in the example 11111100 would be FFFFFFFC for reg/rgu files or 252 for xml/provxml files)

This way you can get whatever combination of screens you want.

My current rom has only tap screen (no alignment, no password, etc) and works fine.

If you do not get the expected results, most probably is not because you did it wrong but rather there is some other code replacing yours. My recommendation is to calculate the hex dec and binary values corresponding to the combination of screens that get loaded and then use the search function included in a visual kitchen to locate the file hindering your intended customization (Or simply look for the reg keys). Most of the roms will have as much as 3 or 4 places where welcome values are define (sys, oem, ext and yours !!). If you are not so patient create and ext package called zzz_whatever and in the files directory place a app.REG file so all values are overwritten. Make sure your reg or xml file does not mix with other non tested code since it may also happen that the file is not executed correctly and its rollbacked. When using provxml files non tested code should be placed behind so you can call mxipupdate_zzz01_tested and mxipupdate_zzz02_nontested to get the expected order. I think the order things get loaded are provxml, rgu, reg, xml and inside each group, package folder name and then file name.

Hope it helps, regards

Binary	Hex	Dec
		
10000000	80	128
10000001	81	129
10000010	82	130
10000011	83	131
10000100	84	132
10000101	85	133
10000110	86	134
10000111	87	135
10001000	88	136
10001001	89	137
10001010	8A	138
10001011	8B	139
10001100	8C	140
10001101	8D	141
10001110	8E	142
10001111	8F	143
10010000	90	144
10010001	91	145
10010010	92	146
10010011	93	147
10010100	94	148
10010101	95	149
10010110	96	150
10010111	97	151
10011000	98	152
10011001	99	153
10011010	9A	154
10011011	9B	155
10011100	9C	156
10011101	9D	157
10011110	9E	158
10011111	9F	159
10100000	A0	160
10100001	A1	161
10100010	A2	162
10100011	A3	163
10100100	A4	164
10100101	A5	165
10100110	A6	166
10100111	A7	167
10101000	A8	168
10101001	A9	169
10101010	AA	170
10101011	AB	171
10101100	AC	172
10101101	AD	173
10101110	AE	174
10101111	AF	175
10110000	B0	176
10110001	B1	177
10110010	B2	178
10110011	B3	179
10110100	B4	180
10110101	B5	181
10110110	B6	182
10110111	B7	183
10111000	B8	184
10111001	B9	185
10111010	BA	186
10111011	BB	187
10111100	BC	188
10111101	BD	189
10111110	BE	190
10111111	BF	191
11000000	C0	192
11000001	C1	193
11000010	C2	194
11000011	C3	195
11000100	C4	196
11000101	C5	197
11000110	C6	198
11000111	C7	199
11001000	C8	200
11001001	C9	201
11001010	CA	202
11001011	CB	203
11001100	CC	204
11001101	CD	205
11001110	CE	206
11001111	CF	207
11010000	D0	208
11010001	D1	209
11010010	D2	210
11010011	D3	211
11010100	D4	212
11010101	D5	213
11010110	D6	214
11010111	D7	215
11011000	D8	216
11011001	D9	217
11011010	DA	218
11011011	DB	219
11011100	DC	220
11011101	DD	221
11011110	DE	222
11011111	DF	223
11100000	E0	224
11100001	E1	225
11100010	E2	226
11100011	E3	227
11100100	E4	228
11100101	E5	229
11100110	E6	230
11100111	E7	231
11101000	E8	232
11101001	E9	233
11101010	EA	234
11101011	EB	235
11101100	EC	236
11101101	ED	237
11101110	EE	238
11101111	EF	239
11110000	F0	240
11110001	F1	241
11110010	F2	242
11110011	F3	243
11110100	F4	244
11110101	F5	245
11110110	F6	246
11110111	F7	247
11111000	F8	248
11111001	F9	249
11111010	FA	250
11111011	FB	251
11111100	FC	252
11111101	FD	253
11111110	FE	254
11111111	FF	255

 

[RoryB]

i must be doing something wrong.. no matter what i try it's not changing the boot setup

it's still going 'tap', 'calibrate', 'time/date', and 'password'....

all i want is Tap and calibrate!!!!

this is doing my head in. i'd appreciate any other ideas???

many thanks to anyone who may be able to help

Chris

Check the registry after you flash and the ROM is finished setting up. Does it read the values you set? Maybe there is another provxml or rgu setting it to a wrong value.

 

[chrisd1a1]

I will try to explain how to get any number you need:

1. Put this table in an excel,
2. Find the 8 digits corresponding to EACH of the screens wanted (eg. tap screen is FD or 253 and align screen is FE or 254 )
3. Tap each digit in a column (one line per screen wanted)
4. calculate the minimum of each column and get the 8 digits (in the example, min of 11111101 and 11111110 is 11111100).
5. If you use provxml go the other way round and with the total calculated find the Dec Value (3rd column) corresponding to the 8 digits (in the example 11111100 would be FFFFFFFC for reg/rgu files or 252 for xml/provxml files)

This way you can get whatever combination of screens you want.

My current rom has only tap screen (no alignment, no password, etc) and works fine.

If you do not get the expected results, most probably is not because you did it wrong but rather there is some other code replacing yours. My recommendation is to calculate the hex dec and binary values corresponding to the combination of screens that get loaded and then use the search function included in a visual kitchen to locate the file hindering your intended customization (Or simply look for the reg keys). Most of the roms will have as much as 3 or 4 places where welcome values are define (sys, oem, ext and yours !!). If you are not so patient create and ext package called zzz_whatever and in the files directory place a app.REG file so all values are overwritten. Make sure your reg or xml file does not mix with other non tested code since it may also happen that the file is not executed correctly and its rollbacked. When using provxml files non tested code should be placed behind so you can call mxipupdate_zzz01_tested and mxipupdate_zzz02_nontested to get the expected order. I think the order things get loaded are provxml, rgu, reg, xml and inside each group, package folder name and then file name.

Hope it helps, regards

Binary	Hex	Dec
		
10000000	80	128
10000001	81	129
10000010	82	130
10000011	83	131
10000100	84	132
10000101	85	133
10000110	86	134
10000111	87	135
10001000	88	136
10001001	89	137
10001010	8A	138
10001011	8B	139
10001100	8C	140
10001101	8D	141
10001110	8E	142
10001111	8F	143
10010000	90	144
10010001	91	145
10010010	92	146
10010011	93	147
10010100	94	148
10010101	95	149
10010110	96	150
10010111	97	151
10011000	98	152
10011001	99	153
10011010	9A	154
10011011	9B	155
10011100	9C	156
10011101	9D	157
10011110	9E	158
10011111	9F	159
10100000	A0	160
10100001	A1	161
10100010	A2	162
10100011	A3	163
10100100	A4	164
10100101	A5	165
10100110	A6	166
10100111	A7	167
10101000	A8	168
10101001	A9	169
10101010	AA	170
10101011	AB	171
10101100	AC	172
10101101	AD	173
10101110	AE	174
10101111	AF	175
10110000	B0	176
10110001	B1	177
10110010	B2	178
10110011	B3	179
10110100	B4	180
10110101	B5	181
10110110	B6	182
10110111	B7	183
10111000	B8	184
10111001	B9	185
10111010	BA	186
10111011	BB	187
10111100	BC	188
10111101	BD	189
10111110	BE	190
10111111	BF	191
11000000	C0	192
11000001	C1	193
11000010	C2	194
11000011	C3	195
11000100	C4	196
11000101	C5	197
11000110	C6	198
11000111	C7	199
11001000	C8	200
11001001	C9	201
11001010	CA	202
11001011	CB	203
11001100	CC	204
11001101	CD	205
11001110	CE	206
11001111	CF	207
11010000	D0	208
11010001	D1	209
11010010	D2	210
11010011	D3	211
11010100	D4	212
11010101	D5	213
11010110	D6	214
11010111	D7	215
11011000	D8	216
11011001	D9	217
11011010	DA	218
11011011	DB	219
11011100	DC	220
11011101	DD	221
11011110	DE	222
11011111	DF	223
11100000	E0	224
11100001	E1	225
11100010	E2	226
11100011	E3	227
11100100	E4	228
11100101	E5	229
11100110	E6	230
11100111	E7	231
11101000	E8	232
11101001	E9	233
11101010	EA	234
11101011	EB	235
11101100	EC	236
11101101	ED	237
11101110	EE	238
11101111	EF	239
11110000	F0	240
11110001	F1	241
11110010	F2	242
11110011	F3	243
11110100	F4	244
11110101	F5	245
11110110	F6	246
11110111	F7	247
11111000	F8	248
11111001	F9	249
11111010	FA	250
11111011	FB	251
11111100	FC	252
11111101	FD	253
11111110	FE	254
11111111	FF	255

Check the registry after you flash and the ROM is finished setting up. Does it read the values you set? Maybe there is another provxml or rgu setting it to a wrong value.

looks like you guys are right about something messing with this.

i set it to FC as advised but when i checked the reg on the build it's showing AC. i'm going to try a variation to see what happens..

i really appreciate the advice, just wish i could figure the fix

thanks for the help i appreciate it

Chris

 

[twisted]

hi,
try to search in the rgu of your OEMDrivers.
maybe there is a registry entry that is replacing your registry.

regards,

twisted

 

[cruiserrr]

i really appreciate the advice, just wish i could figure the fix

What are you using for building the rom? I am pretty familiar with Ervius Visual Kitchen and it is quite straigth forward to use the search tool. Even if you use another kitchen you can download evk, put your files in the ext folder and do the search. Good luck!

 

[trueg]

I find Agent Ransack is a handy tool for searching the contents of files.

As a test you can set the registry the way you like and then run welcome.exe to see if the behaviour is the way you expect.