RyanVM.net Discussion Board Forum Index RyanVM.net Discussion Board

 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

[SOLVED] Error "icfgnt.dll, Windows cannot load the Int

 
Post new topic   Reply to topic    RyanVM.net Discussion Board Forum Index -> Update Pack Discussion
View previous topic :: View next topic  
Author Message
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Tue Feb 28, 2006 12:37 am    Post subject: [SOLVED] Error "icfgnt.dll, Windows cannot load the Int Reply with quote

Hallo all,

RyanVM is a great peace of work, thanks to all who have contributed to this project.

But at its current stage it seems to be only usable for users making CDs because of this strange error "icfgnt.dll, Windows cannot load the Internet Configuration Library" at T15 of the installation when startet by winnt.exe or winnt32.exe

There were some discussions of this problem in this forum and at msfn, see for example:

http://www.ryanvm.net/forum/viewtopic.php?t=660

but all of them I saw ended up with no solution or with some kind of "trial an error" solution like first integrating SP1a, then SP2 which might have worked for someone without realy knowing why.

So I thought its time to debug this problem.

I took a clean XPSP2 with a nearly empty $OEM$ directory and a nearly empty unattend.txt. The installation works fine using winnt.exe. Next step was applaying RyanVM's Updatepack 2.0.2a and doing the same installation again: the error is there!

At this point the system has been reseted und rebooted with a BartPE-CD.
Looking in setuperr.log the first entry is:

Quote:
Error:
C:\$WIN_NT$.~LS\i386\TSHOOT.dll was not copied to C:\WINNT\help\TSHOOT.dll because of the
following error: The operation was canceled by the user.


Searching Drive C:\ showed that the source file to be copied C:\$WIN_NT$.~LS\i386\TSHOOT.dll
does not exist however the destination C:\WINNT\help\TSHOOT.dll does.

Doing some experiments at this point (restarting the installation) showed that always if a file to be copied in GUI-Mode is missing the above error is triggered!

Conclusion of this is: all kind of missing files could trigger this error, watch the first message in %WinDir%\setuperr.log to determine what file caused the error.

Next question was: Why is TSHOOT.dll missing in C:\$WIN_NT$.~LS\i386?
Answer: This is the normal behavior. Before Textmode setup there are about 5500 files in C:\$WIN_NT$.~LS\i386 after that there are about 2300. All files having a number in the eighth field like "20" in

Quote:
tshoot.inf = 1,,,,,,,20,0,0


are decompressed to their destination (%WinDir%\inf in this case) and get deleted in C:\$WIN_NT$.~LS\i386, in other words, they are moved while files with an empty eighth field like

Quote:
tshoot.cab = 1,,,,,,,,3,3


seem to stay untouched in textmode.
This is the same with and without RyanVMs Updatepack applied. But where is the differnce?

Studying setuplog.txt of a system without Updatepack shows that there is no try to copy tshoot.dll in GUI mode. There seems to be a diffrent interpratation of the flags field "4" in [Copyfiles] Section in tshoot.inf:

Quote:
bnts.dll,,,4
TSHOOT.dll,,,4
sniffpol.dll,,,4
sstub.dll,,,4


The MSDN online documentation of the flags field says:

Quote:
0x00000004 (COPYFLG_NOVERSIONCHECK)
Ignore file versions and write over existing files in the destination directory. This flag and the next two are mutually exclusive. This flag is irrelevant to digitally signed INF files.


Since the tshoot.inf file is the same in both cases it seems without Updatepack to be interpreted as digitally signed and with it as not digitally signed. Or there are diffrent setup modules with and without Updatepack. I can't explain this.

Next Qustion is: What we can do to make the install proceed without errors?
Answer 1: Changing tshoot.inf so that it not tries to copy these files. But there is no guess, if this would have any side effects.
Answer 2: Manipulate the txtsetup.sif that these files are not moved but copied in textmode setup.

Investigating if there are already files that were copied and what syntax is used to declare this I found that there are such files and that their common property in txtsetup.sif is the value "16" in the [FileFlags] section like

Quote:
kbdclass.sys = 16


So I simply added to [FileFlags]

Quote:
BNTS.DLL = 16
TSHOOT.DLL = 16
SNIFFPOL.DLL = 16
SSTUB.DLL = 16


what brought my installation to a similar problem in netupnph.inf. I had to add 6 more files:

Quote:
SSDPSRV.DLL = 16
SSDPAPI.DLL = 16
UPNP.DLL = 16
UPNPHOST.DLL = 16
UPNPCONT.EXE = 16
UDHISAPI.DLL = 16


And that's all so far to make my unattend setup run without errors. Since there are still no OEM drivers and no values under [Components] in unattend.txt the destination system is not usable. But before I go on I wanted to share my solution with others.

My next Question is: Is there a possibility to insert these lines via entries.ini?
Back to top
View user's profile Send private message
Siginet
Site Admin


Joined: 27 May 2005
Posts: 2892
Location: Planet Earth

PostPosted: Tue Feb 28, 2006 1:54 am    Post subject: Reply with quote

This is actually a good thread. It is a problem that I think has been around for a long time. If this becomes a true fix I will implement this into the integrator.

And yes you can add these changes into an entries file by using ExtraFileEdits.

Welcome to the forums JSe. Wink
_________________

--Siginet--

Techware
Your Virtual Technician
Computer Management Software
Back to top
View user's profile Send private message Visit poster's website
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Tue Feb 28, 2006 11:01 am    Post subject: Reply with quote

I've also heard from users in the past that removing unsigned INFs (such as swflash.inf) fixes the problem.
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Tue Feb 28, 2006 2:06 pm    Post subject: Reply with quote

WOW! Very Happy Finally someone tries to debug this problem (which has existed since I first tried any RyanVM Update Pack - from 1.2.0 in fact !) - This would truly make RyanVM pack complete...

(I wish I had more time to try to do this...)

Awesome work there, I hope you crack this mystery completely !
Best of luck !
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Tue Feb 28, 2006 10:36 pm    Post subject: Reply with quote

Now I have cleaned up my environment with a fresh copy of XPSP2, integrated RyanVM's Updatepack 2.0.3, added my drivercollection (its similar to BTS's collection using M1 but it exists longer than BTS's one - we do unattended installations since 1997 beginning with WinNT 4.0 SP1), added the Netware Client and used our "normal" unattend.txt. The installation went fine without the famos error.

There was still a "missing" file, which did not trigger the error but made an entry to setuperr.log.
It's sapicpl.hlp, which I will add to the [FileFlags]

It seems to me that the problem is realy solved.

I would like to hear from others if they can acknowledge my solution.

Quote:
If this becomes a true fix I will implement this into the integrator.


That would be great, in my cleaned environment I did it by hand for now.

Next im going to try it with German version of XP what is my real need at the end.
Back to top
View user's profile Send private message
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Wed Mar 01, 2006 12:53 am    Post subject: Reply with quote

Jse wrote:
So I simply added to [FileFlags]

BNTS.DLL = 16
TSHOOT.DLL = 16
SNIFFPOL.DLL = 16
SSTUB.DLL = 16


what brought my installation to a similar problem in netupnph.inf. I had to add 6 more files:

SSDPSRV.DLL = 16
SSDPAPI.DLL = 16
UPNP.DLL = 16
UPNPHOST.DLL = 16
UPNPCONT.EXE = 16
UDHISAPI.DLL = 16


I have tested this with many addons and RyanVM Update Pack 2.0.3 and I can confirm that this fixed the "icfgnt.dll" error, although I did get a few missing files...

in WINNT.EXE mode:
cyclad-z.inf <-- Adding to FileFlags (cyclad-z.inf = 16) doesn't work
cyclom-y.inf <-- Adding to FileFlags (cyclom-y.inf = 16) doesn't work
utopia~1.wav
utopia~2.wav
utopia~3.wav
utopia~4.wav

after 2nd reboot in GUI mode:
The "LANG" subfolder is not being copied as well to $WIN_NT$.~LS folder and setup complains about files that were in them (like msmincho.ttc and msgothic.ttc and several .FON files) yet WINNT.EXE apparently didn't even try to copy them...
(here's something related to this: http://support.microsoft.com/kb/241063/EN-US/ - I was using a RegionalSettings part in my WINNT.SIF to install additional language support...)

Also another file:
speech.chm

You're on the right track JSe
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox


Last edited by n7Epsilon on Wed Mar 01, 2006 8:33 am
Back to top
View user's profile Send private message
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Wed Mar 01, 2006 8:21 am    Post subject: Reply with quote

n7Epsilon, thanks for your testing.
Quote:
You're on the right track JSe Wink)


Quote:
The "LANG" subfolder is not being copied as well to $WIN_NT$.~LS folder

That's no bug, it's a feature. You will have to specify /rx:lang when using winnt.exe and /copysource:"lang" when using winnt32.exe.

Quote:
Also another file:
speech.chm

speech.chm and sapicpl.hlp are "sisterfiles" already under my own investigation.

Quote:
although I did get a few missing files...

in WINNT.EXE mode:
cyclad-z.inf
cyclom-y.inf
utopia~1.wav
utopia~2.wav
utopia~3.wav
utopia~4.wav

This does not happen to me. Please verify, that these files are present in your sourcedir (from where you start winnt.exe) and make sure that their long names are the same as their short names in source directory. This may depend on the type of the filesystem and the operating system where you start winnt.exe from. In my case the filesystem is on a Netware server and I start winnt.exe under MSDOS 7.10 coming from WIN98 SE so it may not be representative for your problem.
Back to top
View user's profile Send private message
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Wed Mar 01, 2006 8:39 am    Post subject: Reply with quote

@JSe
I am also launching setup from WINNT.EXE and under Windows 98SE DOS. The filesystem is on CD-ROM...

I have discovered why the files are not copying...

When I run mkisofs.exe to make the ISO, it changed the - and ~ to _ in the filename on the ISO9660 filesystem read by DOS (with SHSUCDX driver), while in TextMode Windows reads Joliet filesystem which correctly finds the files...

So they cannot be found ! I am fixing this now and will test again...

EDIT: Found a workaround - Load DOSLFN before running WINNT.EXE

-- No errors in WINNT.EXE mode now
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Wed Mar 01, 2006 10:18 am    Post subject: Reply with quote

Quote:
When I run mkisofs.exe to make the ISO, it changed the - and ~ to _ in the filename on the ISO9660 filesystem read by DOS (with SHSUCDX driver), while in TextMode Windows reads Joliet filesystem which correctly finds the files...


You may try to change some mkisofs options:
1. use -no-iso-translate
From the mkisofs manpage:
Quote:
-no-iso-translate
Do not translate the characters '#' and '~' which are
invalid for iso9660 filenames. These characters are
though invalid often used by Microsoft systems.
This violates the ISO9660 standard, but it happens to
work on many systems. Use with caution.


2. Do not use -J (Joliet extension), the "native" names used in DOS then will be the same as in Windows and also do not use -R (Rock Ridge extension) under LINUX in this case for the same reason.
Back to top
View user's profile Send private message
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Wed Mar 01, 2006 10:39 am    Post subject: Reply with quote

JSe wrote:
You may try to change some mkisofs options:
1. use -no-iso-translate
From the mkisofs manpage:
Quote:
-no-iso-translate
Do not translate the characters '#' and '~' which are
invalid for iso9660 filenames. These characters are
though invalid often used by Microsoft systems.
This violates the ISO9660 standard, but it happens to
work on many systems. Use with caution.


I discovered that after editing the post...
I can DEFINITELY CONFIRM that FileFlags fixed WINNT support for RyanVM Update Pack...

Maybe Ryan should add this into the Update Pack's entries.ini ...

Here's what I added into my FileFlags section:

BNTS.DLL = 16
TSHOOT.DLL = 16
SNIFFPOL.DLL = 16
SSTUB.DLL = 16
SSDPSRV.DLL = 16
SSDPAPI.DLL = 16
UPNP.DLL = 16
UPNPHOST.DLL = 16
UPNPCONT.EXE = 16
UDHISAPI.DLL = 16
SAPICPL.HLP = 16
SPEECH.CHM = 16

(Adding Speech.chm fixed it)...
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Wed Mar 01, 2006 3:42 pm    Post subject: Modifications in AddOn CAB form for Integrator Reply with quote

@JSe
I have tested and confirmed that your fix works perfectly in several WINNT.EXE installs...

Here are the modifications created in an AddOn CAB form, tested it now and it works.
http://rapidshare.de/files/14456190/WINNTfix_AddOn.cab.html
MD5: FF640414EAE25EE01830C60C916535F7

Credits to JSe for discovering this amazing workaround/fix !
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Wed Mar 01, 2006 5:47 pm    Post subject: Reply with quote

I'll most definitely include those lines in the next update pack/integrator release.

Nice detective work!
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Thu Mar 02, 2006 5:00 am    Post subject: Reply with quote

I've posted in the nLite forum (on msfn.org) about this and linked back to here.

EDIT: and tested a WINNT32.EXE install without any problems by installing over a network share through BartPE...
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Thu Mar 02, 2006 11:50 am    Post subject: Reply with quote

@n7Epsilon,
Many thanks for the file WINNTfix_AddOn.cab.html and all your testings you have done to verify my solution.

I'm going to do a final test tonight with a new unattend.txt having a complete list under [Components] where all components are set to "On"
This should figure out if the list of files to be set under [FileFlags] is already complete or not.
Back to top
View user's profile Send private message
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Thu Mar 02, 2006 11:57 am    Post subject: Reply with quote

All of the tests I have carried out (and still am Wink ) were with standard Windows XP installs (without a Components section in WINNT.SIF) and so far I have had no problems...

Keep investigating though... I am also testing different install configurations...
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
nuhi



Joined: 19 Feb 2005
Posts: 36

PostPosted: Thu Mar 02, 2006 1:31 pm    Post subject: Reply with quote

JSe, nice info.

My solution was removing entries from INF's calling those files since they are already copied where they should by txtsetup.sif.
Detected them while configuring a year ago.

However for some reason that wasn't enough to solve icfgnt.dll error, only manual install other missing files.

Anyway your solution is much cleaner, thanks.
Back to top
View user's profile Send private message Visit poster's website
Siginet
Site Admin


Joined: 27 May 2005
Posts: 2892
Location: Planet Earth

PostPosted: Thu Mar 02, 2006 1:55 pm    Post subject: Reply with quote

I went ahead and added a new [txtsetup_fileflags] section to the integrator to process in the entry files (As requested by RyanVM). So now there is added support to fix this issue. Smile

Thanx JSe for finding a solution!
_________________

--Siginet--

Techware
Your Virtual Technician
Computer Management Software
Back to top
View user's profile Send private message Visit poster's website
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Thu Mar 02, 2006 7:26 pm    Post subject: Reply with quote

@n7Epsilon
Quote:
(without a Components section in WINNT.SIF) and so far I have had no problems...
Please note that not to specify a component under [Components] means that the default setting for this component will be used. This default is in many cases "= Off". An example is the Fax console (Start --> Programs --> Accessories --> Communications --> Fax --> Fax Console) which I would guess you don't have after your installation without [Components] section.
For more information about this you may consult the file ref.chm. It's normaly in the file \SUPPORT\TOOLS\DEPLOY.CAB on XPCDs. Make sure to use a XPSP2 version of this file dated 07/17/2004. It's a "must have" if you make your own unattend.txt / winnt.sif.

But luckily even with all components set "= On" no more files than the twelve we already know are missing.
Back to top
View user's profile Send private message
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sat Mar 04, 2006 5:56 pm    Post subject: Reply with quote

I'm seeing this error when I try an install with the relevant flags added:


I'm doing a winnt32.exe install started from inside Windows. The only option I selected was to copy the files from the CD to the hard drive. The CD itself is a standard XP SP2 CD with no unattended features at all. Is this another file which needs the 16 flag?
Back to top
View user's profile Send private message Visit poster's website
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sat Mar 04, 2006 7:32 pm    Post subject: Reply with quote

Setting MCHGRCOI.DLL=16 in [FileFlags] took care of that one, but now I'm getting cga40850.fon Rolling Eyes

Oh well, I guess I'll be adding a few more flags to the list Razz
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sat Mar 04, 2006 10:51 pm    Post subject: Reply with quote

I'm getting a bunch of fonts. I've got a feeling it's from the changed intl.inf
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Sun Mar 05, 2006 9:59 am    Post subject: Reply with quote

Ryan,

the error on the snapshot shows that you are at T39, means short after start of GUImode. So I assume somthing general went wrong.

Quote:
The only option I selected was to copy the files from the CD to the hard drive
Which option did you use?

Quote:
unattended features at all
... you did not have a winnt.sif nor a unattend.txt, right?

And still a last question: On which drive(letter) was the running Windows you started winn32.exe from?

To help you debug the problem you can send me a PM with the file txtmdir.txt
Code:
dir c:\ /s > txtmdir.txt
you should make bitween textmode and GUImode setup.
Back to top
View user's profile Send private message
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sun Mar 05, 2006 10:18 am    Post subject: Reply with quote

JSe wrote:
Which option did you use?
The one in the advanced options to copy all setup files to the hard disk.
Quote:
you did not have a winnt.sif nor a unattend.txt, right?
Correct
Quote:
And still a last question: On which drive(letter) was the running Windows you started winn32.exe from?
C:
Quote:
To help you debug the problem you can send me a PM with the file txtmdir.txt
Code:
dir c:\ /s > txtmdir.txt
you should make bitween textmode and GUImode setup.
I don't think that's necessary yet. All of the files it's complaining about are from intl.inf, which is updated by the pack (so it probably isn't being seen as signed since the CAT files aren't loaded yet). I found the sections in intl.inf where each file is listed in the exact order that GUI setup was complaining about. Adding them has seemed to work so far (though I'm getting more files as I go).

One thing I am worried about is that if I point GUI setup to d:\i386 for those missing files, things go OK. However, I then run into a "kbdbhc.dll can't be found" error message, which is a file added by my pack (and adding an =16 flag to it makes no difference). It's in dosnet.inf, so I'm not really sure why that's happening.
Back to top
View user's profile Send private message Visit poster's website
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sun Mar 05, 2006 10:30 am    Post subject: Reply with quote

This is what I'm talking about.

What's also interesting is that if I cancel the dialog, I don't get any further file missing errors (not even the other 3 keyboard layout DLLs that go along with kbdbhc.dll)

The good news is that I apparently got all the needed files from intl.inf, as I wasn't getting any other prompts about missing files this time around Smile
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sun Mar 05, 2006 1:43 pm    Post subject: Reply with quote

OK, adding the below entries fixes all but the kbdbhc.dll problem.
Code:
MCHGRCOI.DLL=16
CGA40850.FON=16
CGA40WOA.FON = 16
CGA80850.FON=16
CGA80WOA.FON=16
COURE.FON=16
COURF.FON=16
DOSAPP.FON=16
EGA40850.FON=16
EGA40WOA.FON=16
EGA80850.FON=16
EGA80WOA.FON=16
SERIFE.FON=16
SERIFF.FON=16
SMALLE.FON=16
SMALLF.FON=16
SSERIFE.FON=16
SSERIFF.FON=16
VGA850.FON=16
VGA860.FON=16
VGA863.FON=16
VGA865.FON=16
VGAFIX.FON=16
VGASYS.FON=16
AGT0407.DLL=16
AGT040C.DLL=16
AGT0410.DLL=16
AGT0C0A.DLL=16
AGT0416.DLL=16
AGT0406.DLL=16
AGT0413.DLL=16
AGT040B.DLL=16
AGT0414.DLL=16
AGT0816.DLL=16
AGT041D.DLL=16
AGT0407.HLP=16
AGT040C.HLP=16
AGT0410.HLP=16
AGT0C0A.HLP=16
AGT0416.HLP=16
AGT0406.HLP=16
AGT0413.HLP=16
AGT040B.HLP=16
AGT0414.HLP=16
AGT0816.HLP=16
AGT041D.HLP=16
KBDNEC.DLL=16

_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sun Mar 05, 2006 3:11 pm    Post subject: Reply with quote

I'm also getting a lot of unsigned hardware notices during device detection that I don't get if I boot from the CD and install Windows that way.
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Sun Mar 05, 2006 3:48 pm    Post subject: Reply with quote

Quote:
Quote:
And still a last question: On which drive(letter) was the running Windows you started winn32.exe from?
C:

So this means your destination already has a running Windows (XP?)?. And if so, do you install over the existing Windows or do you a seperate destination path? If you install over an existing path this would explain some copy problems since there may be more files already existing than on a plain destination drive.

Quote:
One thing I am worried about is that if I point GUI setup to d:\i386 for those missing files, things go OK
This seems no good solution to me because you "show" the installer the files from CD. For the most of them this may be ok, but there are some files that are renamed in textmode and in these cases the installer sees the unrenamed versions of these files.

Quote:
This is what I'm talking about.
This snapshoot shows that you (or the installer) are missing the \i386 subdir in C:\$win_nt$.~ls while searching the kbdbhc.dll.

Locking at txtsetup.sif I found, that the for kbd*.dll's are the only files with a diffrent schema in their entry compared to the other entries added by Update pack.
Code:
...
ifxcardm.dll = 100,,,,,,,2,0,0
kbdbhc.dll   = 1,,,,,,_x,2,0,0
kbdiultn.dll = 1,,,,,,_x,2,0,0
kbdnepr.dll  = 1,,,,,,_x,2,0,0
kbdpash.dll  = 1,,,,,,_x,2,0,0
...


I do not know the complete syntax of these entries (it would be nice if somebody could teach me on this), but the first number =1 means the file is from original XP without SP, = 100 means its from SPx CD. Since Update Pack replaces these files it seems reasonable to me to change their entries to:
Code:
kbdbhc.dll   = 100,,,,,,_x,2,0,0
kbdiultn.dll = 100,,,,,,_x,2,0,0
kbdnepr.dll  = 100,,,,,,_x,2,0,0
kbdpash.dll  = 100,,,,,,_x,2,0,0


Btw., What tagfiles (win51, win51ip, win51ip.sp2) does your cd have?

I'm not sure if it helps, but I would try this next.
Back to top
View user's profile Send private message
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sun Mar 05, 2006 3:55 pm    Post subject: Reply with quote

JSe wrote:
So this means your destination already has a running Windows (XP?)?. And if so, do you install over the existing Windows or do you a seperate destination path? If you install over an existing path this would explain some copy problems since there may be more files already existing than on a plain destination drive.
I have it remove the existing Windows directory prior to copying files when textmode setup prompts about it.
Quote:
This seems no good solution to me because you "show" the installer the files from CD. For the most of them this may be ok, but there are some files that are renamed in textmode and in these cases the installer sees the unrenamed versions of these files.
I agree Razz
Quote:
Locking at txtsetup.sif I found, that the for kbd*.dll's are the only files with a diffrent schema in their entry compared to the other entries added by Update pack.
I'll change them to 100 and see what happens.
Quote:
Btw., What tagfiles (win51, win51ip, win51ip.sp2) does your cd have?
You got it Smile

You'll probably find this site to be useful too.
http://gosh.msfnhosting.com/txtsetup.htm
Back to top
View user's profile Send private message Visit poster's website
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sun Mar 05, 2006 4:51 pm    Post subject: Reply with quote

Well, changing it from 1 to 100 didn't make the problem go away. nuhi says it's safe to remove the reference to it in intl.inf, but I'm nervous about changing that.
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Sun Mar 05, 2006 6:42 pm    Post subject: Reply with quote

I also would not change intl.inf. To be consequential in this case I would remove KB897338.

But to make the right thing I would go the hard way of debug the problem. That means
1. install until the error comes up and study setupact.log, setupapi.log, setuperr.log and setuplog.txt. This can even be done after the installation is complete, but its easier to reset the PC at the error message and boot with BartPE to see the files named.
2. stop the installation after copymode and after textmode to see if the missing files are present, are in the sourcelocation or are already in their destination location. I did this by booting with a BartPE-CD between the setup phases and copied c:\ to a network drive to do some analysis while the install went on.

And I also think that the way you started the installation is not very common. Most people starting an installation with winnt.exe or winnt32.exe do unattended setups from a network share. And this has been working for n7Epsilon
Quote:
and tested a WINNT32.EXE install without any problems by installing over a network share through BartPE...
and for me with winnt.exe.

I will try a non unattend setup with winnt.exe from my network share to see if your error happens also in this environment.
Back to top
View user's profile Send private message
JSe



Joined: 27 Feb 2006
Posts: 32
Location: Germany

PostPosted: Sun Mar 05, 2006 8:54 pm    Post subject: Reply with quote

Quote:
I will try a non unattend setup with winnt.exe from my network share to see if your error happens also in this environment.

I did so (had a clean 10 GB FAT32, booted MSDOS 7.10 with Nwclient from CD, started winnt.exe from distribution share without any options) it installed wihout any problems (I stopped the installation at T33 since I was sure the problem zone had been passed).
And then I did the same with winnt32.exe (had a clean 10 GB NTFS, booted BartPE also with NWclient and started winnt32.exe from the same distribution share without any options) and also without any errors to T33.
In both cases I had only the 12 files under FileFlags which had been discovered by n7Epsilon and by me.
Back to top
View user's profile Send private message
RyanVM
Site Admin


Joined: 23 Nov 2004
Posts: 5156
Location: Pennsylvania

PostPosted: Sun Mar 05, 2006 9:10 pm    Post subject: Reply with quote

So starting it from within Windows seems to be the problem. Now the question is why...
_________________
Get up to $200 off on hosting from the same people who host this website!
http://www.ryanvm.net/forum/viewtopic.php?t=2357
Back to top
View user's profile Send private message Visit poster's website
Siginet
Site Admin


Joined: 27 May 2005
Posts: 2892
Location: Planet Earth

PostPosted: Sun Mar 05, 2006 10:52 pm    Post subject: Reply with quote

Well.. at least we have fixed most install methods now. Very Happy

Thanks to everyone here for the help!
_________________

--Siginet--

Techware
Your Virtual Technician
Computer Management Software
Back to top
View user's profile Send private message Visit poster's website
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Mon Mar 06, 2006 1:55 am    Post subject: Reply with quote

A lot has happened here (and I've not had much time to check)...

@RyanVM All of the tests I have conducted with winnt.exe and winnt32.exe are unattended using this method: I use the Setup.exe / Presetup.cmd hack to execute the following commands before GUI mode (effectively simulating winnt.sif but I modify $winnt$.inf directly)

From my PreSetup.cmd:
Code:

set cmdexec=fedit -add -create -once -f "%SystemRoot%\SYSTEM32\$WINNT$.INF" -s
%cmdexec% unattended -l "unattendmode=\"readonly\""
%cmdexec% unattended -l "oempreinstall=\"yes\""
%cmdexec% unattended -l "driversigningpolicy=\"ignore\""
%cmdexec% unattended -l "nondriversigningpolicy=\"ignore\""
%cmdexec% guiunattended -l "oemskipregional=\"1\""
%cmdexec% guiunattended -l "oemskipwelcome=\"1\""
%cmdexec% regionalsettings -l "LanguageGroup=13,17,3,2,5,16,4,12,15,7,8,10,11,9,6,14,1"
%cmdexec% regionalsettings -l "Language=00000409"
If exist Setup.exe ren Setup.exe SetupOld.exe
If exist SetupGUI.exe ren SetupGUI.exe Setup.exe
Start "Ignore Non Signed Drivers" WatchDriverSigningPolicy.exe
Start "Installing Windows XP..." /WAIT SETUP.EXE %*


Same thing for WINNT.EXE ... (but I specify /rx:LANG) to copy the extra LANG files for the extra languages specified.

And I have not been gettings any file copy errors using the AddOn I created (which contains JSe's original fixes)...

- winnt32.exe run over a network share.
- winnt.exe started from the command line.

In Intl.inf, could this line be causing any problems ?
Quote:
LayoutFile = layout.inf


http://www.microsoft.com/whdc/archive/W2inf.mspx
has information about LayoutFile, it appears that Setup is reading Layout.inf somehow ? I know that kbdbhc.dll is not mentioned there (because it's a new file and we can't modify as it is digitally signed..)
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Mon Mar 06, 2006 8:31 am    Post subject: Reply with quote

I have done another test...

Winnt32.Exe via a network share started from BartPE, No Winnt.sif, No Unattend.txt, No Presetup.cmd, No Setup.exe Hack.

I did not check "Install support for East Asian languages", and "Copy Setup Files from CD" was checked and greyed out (since I am running via a network share). I did not choose any other options.

I got one unsigned driver warning ("Battery"), I pressed "Continue" and now Setup completed without any errors.

Checked the files RyanVM specified missing, KBDBHC.DLL was properly copied to SYSTEM32 and the .FON files were in the FONTS folder at 33 minutes remaining.

- Also, for completeness' sake, I am using a Windows XP RTM source manually slipstreamed to Service Pack 2 level before integrating the packs and only the 12 entries in my addon.cab (original entries discovered by JSe)

Nothing unusual in setuperr.log ...
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
tridgely



Joined: 18 Jul 2005
Posts: 11

PostPosted: Sun Mar 26, 2006 12:23 am    Post subject: Reply with quote

I just had a question. I've tried using the latest update pack that is supposed to work with winnt32.exe installs, and I'm still having the problem I indicated in this post: http://www.ryanvm.net/forum/viewtopic.php?t=1201.

I want to check that I'm using the same switches with winnt32 that you guys are. I'm running "winnt32.exe /syspart:C /tempdrive:C /unattend:B:\unattend.txt" Is this what you guys are doing also to get it to work? This works for me with other slipstreaming methods (I got it to work with HFSLIP, with only minor edits to txtsetup.sif).
Back to top
View user's profile Send private message AIM Address
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Sun Mar 26, 2006 11:58 am    Post subject: Reply with quote

Can you post your unattend.txt (without your product key and your personal details) please ?

I was launching winnt32.exe without any switches when I was testing...

I will start testing asap...
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox


Last edited by n7Epsilon on Mon Mar 27, 2006 2:18 am
Back to top
View user's profile Send private message
tridgely



Joined: 18 Jul 2005
Posts: 11

PostPosted: Mon Mar 27, 2006 1:06 am    Post subject: Reply with quote

This is my unattend.txt. I'm using an AutoIT script to ask for data, and it fills in the info and makes B:\unattend.txt on the Bart's PE ramdrive. Then disk 0 is cleaned, partitioned, and formatted by diskpart. Afterwords, I start winnt32 with the syspart, tempdrive, and unattend switches.

Code:

[Data]
MsDosInitiated = Yes
Autopartition = 0
FloppyLess = 1
UnattendedInstall = Yes

[Unattended]
OemPreinstall = "Yes"
OemFilesPath="..\$OEM$"
UnattendMode = FullUnattended
UnattendSwitch = Yes
OemSkipEula = Yes
FileSystem = *
WaitForReboot = No
NoWaitAfterTextMode = 1
NoWaitAfterGUIMode = 1
TargetPath = Windows
DriverSigningPolicy = Ignore
NonDriverSigningPolicy = Ignore
OemPnPDriversPath=<long string of bts drivers>

[SystemRestore]
MaximumDataStorePercentOfDisk = 5

[GuiUnattended]
AdminPassword=<password>
AutoLogon = Yes
TimeZone = 035
OEMSkipRegional = 1
OemSkipWelcome = 1

[Components]

[UserData]
ProductKey = <key>
ComputerName = *
FullName = "User"
OrgName = "My Org"

[RegionalSettings]
Language = 0409

[Networking]
InstallDefaultComponents = Yes

[Identification]
JoinWorkgroup = WORKGROUP
Back to top
View user's profile Send private message AIM Address
n7Epsilon
Moderator


Joined: 17 Feb 2005
Posts: 624
Location: Cairo, Egypt

PostPosted: Mon Mar 27, 2006 2:53 am    Post subject: Reply with quote

Please continue discussion here:
http://www.ryanvm.net/forum/viewtopic.php?t=1201
_________________
FGCBA | Reg2Inf | cWnd | PEChecksum | Firefox
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    RyanVM.net Discussion Board Forum Index -> Update Pack Discussion All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group