Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

hi
localised settings were semicoloned out in winnt.sif
KTD all was done, and desktop.ini popped up

looked for files with 21787 in them in the windows folder
syssetup.inf has that string two times.
sysetup.inf has not been altered by anything, tho.
layout.inf has that string for shell.hlp but I dont think that one is relevant either.
desktop.ini was NOT found.
well, that figures, since it was moved out of windows ...

all in all, I am none the wiser.
FAIK, it is not triggered by settings in winnt.sif.

the disabler has to kill the DSP warning popup numerous times, and I imagine the help module comes with it.
maybe that this causes interference with other background processes.
Soon as desktop is loaded, these configuration update popups fly by,  and immediately after that the update ready tray icon is already showing.

I dunno what triggers this.
the double D perhaps? I guess we'll find out when that is fixed.

The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

jtdoom wrote:

hi
localised settings were semicoloned out in winnt.sif
KTD all was done, and desktop.ini popped up

If you get around to it, try a different setting for KTD despite ALL (preferrably PATTERNS using the sample given in the FAQ).
I'm suspecting this to be the culprit...

I'll try myself as soon as Sereby releases the new Update Pack (no use in doing a new CD now I feel).

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

I have got the same problem here... desktop.ini popping up sad
Never had it before with older driverpacks.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

I'll try an English XP version, and after that I think I'll do no more KTD tests until a newer DpsBase becomes available.

the desktop.ini popup must be common enough for Microsoft to write an article about it...

observations;
KTD is not wanted by everyone.
KTD can be done in an existing windows, so if one wants to test all sorts of hardware kit in a machine, one could make a CD that has the files and a cmd script.

The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

mikelm wrote:

for what is this bug tracker for ?  and need i a new account there?
i didn´t know my password here ,because i use cookies and so i forgot it ..

Hi Mikelm
at the main forum page, you can have it resend you the password.
if you remember the email adress you used, that is...
you may have to logout to do that, maybe not...

I saw no such option in profile control panel, and thought the option did not exist.
But, today I saw it on main page, because I logged in from a testrig..

The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

English Pro sp2 retail, RVM, base610, m2, KTD all, GUIrunonce, winnt.sif with locale settings

result, got desktop.ini popup.
I have to run setup on my main machine.
autopatcher tweaked it a little too much (shoulda have run that on a testrig.. tedomme), and some installs prevent me from looking at youtube movies
uninstalls of visual studio 2005, MSDN libraries, arovax, etc.. and reinstalls of java and player don't help.
Will look what I can do with spybot advanved... then prolly run repair setup.
 
not funny at all.

The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

facts are:

xp pro / home sp2 + winnt.sif + sereby´s

with base 6.086 : no desktop.ini  is shown
with base 6.10   : desktop.ini was visible

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

mikelm wrote:

facts are:

xp pro / home sp2 + winnt.sif + sereby´s

with base 6.086 : no desktop.ini  is shown
with base 6.10   : desktop.ini was visible

XP Pro SP2 + winnt.sif + RVM Update Pack

with base 6.08.6: no desktop.ini
with base 6.10   : no desktop.ini


This would lead me to believe the problem is from one of two things:

1. Something in Sereby's Update Pack

2. Something with a non-English source (ex: unicode vs. ansi)

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

RogueSpear wrote:

This would lead me to believe the problem is from one of two things:

1. Something in Sereby's Update Pack

Possible, but I don't think jtdoom is using that, seeing as he's dutch.

2. Something with a non-English source (ex: unicode vs. ansi)

That's more likely as we three (unless someone else has the problem?) are all using a non-English source.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Well it could be possible there is an issue a non-English hotfix that would be in all non-English update packs.  Although I seem to remember someone ran an install with no update pack and got this..  so maybe not.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Thing is, I'm getting this on KTD ALL, whereas I'm not getting this on KTD PATTERNS.

Happened on three different systems.
Very strage, eh?

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Read my Post #7  there i wrote that with pure xp sp2 and base 6.10 i got this desktop.ini  issue ..

perhaps it may be a timing problem ?
as i noticed the finisher in 6.086 works much longer than in base 6.10 .. perhaps there is find the solution beeing on the installation of the drivers or something else..

perhaps windows have not enough tiome to set the attribs from this desktop.ini right so it pop´s up..

Last edited by mikelm (2006-10-13 00:52:47)

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Here's a shot in the dark..  maybe it's in the process of generating .PNF files - which I've found to be totally unnecessary anyway.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

got it on an ENGLISH source too, M2, KTD all, all else default, with locale settings for keyb and country in winnt.sif....
on pure source, or an RVM'ed, with KTD I got me HDsound working and desktop.ini
(the english sources do not have the svcpack.in_ issue)

got a problem on my main machine.
thought drive failure, but the array runs good in its twin.
looks like chip failure...
will crack wrap for two new drives.. to exclude the messup with iastor and AHCI driver versions.
(after all, the drive was originally set up with 5.00xxx the DpsPacked DVD has 5.5xxx and the new floppy has 6.0)
Raid member disks suddenly vanish... during setup.

Last edited by jtdoom (2006-10-13 08:58:43)

The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

something change the attrib from hidden and system to visible an normal ... so the mess comes up.

the desktop.ini already always exist but hidden and as a system file ..

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

hi
plus that this particular one is MOVED, somehow.
I am afraid it is a windows bug which is triggered by KTD

just one R-klik in startup, and delete is what I do

The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

this is not the solution!
i want it hasslefree so i used base 6.086 for xp pro and home and it works fine .. i wait for the next base release and then i triy this.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Ok, I just created a new CD with Sereby's new Update Pack and BASE 6.10 using KTD ALL.
Testing this on the also new Virtual PC 2007 beta (get it here: https://connect.microsoft.com/programde … ilsID=874) I did not get the INI issue anymore.

Since my testing rig is currently missing a HDD, I can't test it in a RealLifeâ„¢ environment, though...



EDIT: Still getting the Double \D\D error, though.
At least we can conclude both are not necessarily related.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Yes, the D\D bug is known and is already solved internally, though I just want to do a few more tests to verify that.

I'm glad it's solved for you. Correct me if I'm wrong, but doesn't this prove that this was NOT caused by DriverPack Sound B 6.10?

Founder of DriverPacks.net — wimleers.com

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Bâshrat the Sneaky wrote:

I'm glad it's solved for you. Correct me if I'm wrong, but doesn't this prove that this was NOT caused by DriverPack Sound B 6.10?

Well, I never claimed it was caused by it. smile
I only stated that it happend whenever I used KTD ALL and never on KTD PATTERNS.

I will need to conduct futher tests before I can be 100% sure but it wouldn't surprise me if it disappeared just as strangely as it hapenned the first time wink

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Hi guys
this  little CMD file did a manual KTD, and that does not produce the popup.
(which does not prove a thing either...)

I actually used ALL PLUS ALL third party.
then I put this on the DVD, together with the extracted files it needs to run.

SET TAGFILE=\DSPdsblr.exe

FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO IF EXIST "%%i:%TAGFILE%" SET CDDRIVE=%%i:

%CDDRIVE%\OEM\BIN\7z.exe x -y -aoa %CDDRIVE%\OEM\DP*.7z -o"%SystemRoot%\DriverPacks"

start %CDDRIVE%\DSPdsblr.exe

%CDDRIVE%\makePNF.exe %SystemRoot%\DriverPacks

taskkill /f /im DSPdsblr.exe


%CDDRIVE%\OEM\BIN\DevPath.exe %SystemRoot%\DriverPacks

exit
The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

it seems that here many people couldn´t read and are blind.

if this people would read the threads carefully they would know that they wrote sh*t. who ofte n should i say the same?

wit ha xp pro sp2 without anything else  only base 6.10 it give the desktop issue
and with the base 6.086 not ..
why is this so hard to understand ?

and also with sereby´s pack  the same effekts ..

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

mikelm wrote:

it seems that here many people couldn´t read and are blind.

if this people would read the threads carefully they would know that they wrote sh*t. who ofte n should i say the same?

If I were you I'd watch my tone because if you continue to flame everyone you won't receive any help...

wit ha xp pro sp2 without anything else  only base 6.10 it give the desktop issue
and with the base 6.086 not ..
why is this so hard to understand ?

Yes, that is you.
If you did carefully read our responses, you aren't the only one experiencing the problem.
Jtdoom and myself are having the same issue.

And we are just reporting ehat helped us curing this problem.
If you don't like this bit of additional information then chose to simply ignore our posts and live with that.
There is absolutely no need to get down on us the way you did!

We are exchanging information here, because that's what a forum is for.
This isn't your own private thread where everyone only has to present a solution to you.

While I'm sure there is enough people around that want to help, you cannot make any demands here.
If you can't live with that maybe you should stop using the DriverPacks...

and also with sereby´s pack  the same effekts ..

If you read my last post you'd know that I am also using Sereby's pack and with the latest edition I am no longer having this issue.
I'm not sure what it is due but it didn't happen anymore and that's fair enough for me ATM.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

I'll do a KTD test on clean english source with no localisation (hooking up my US keyboard even when I still know where most keys are, and know some of the oft used ALT+numerics  by heart.)

you see, the foreign languages have a default localisation.
(otoh, we can count our blessings. I recall US windows98 came with AOL and other crummy stuff set up by default.)

I said that the manual KTD proves nothing, it just proved to me that when i did it that way, it worked.  I did not even use pmtimer either, and the machine is a dual core 2*2Mb cached silly speedmonster..
now, there, I used that word too.

be civil, will ya?
wink

The answer was 42?
Kind regards, Jaak.

Re: [SOLVED BUG #322] Desktop.ini popup after KTD has been applied

Well, it ain't locale

clean US retail, all packs, KTD all, all else default
all locale settings deleted out of winnt
and yes, ini popup.
sound of course works
d\d in windows\driverpacks

if the future build does not do d\d but still does ini popup, I'd have a good look at pmtimer.

svcpack.in_ >> I think uni2ansi is skipped when winnt.sif is present .
(since it does not do what it can do..)

The answer was 42?
Kind regards, Jaak.