CharlyBrown
Content Type
Profiles
Forums
Events
Posts posted by CharlyBrown
-
-
I also tried the latest release 70701a but still no luck for me.
Could you please check the LOGs once more? Is there a patch that can not be integrated and is known to cause Problems?
0 -
I used a new CD-RW media at first: It did not change anything. The next I'll try is the harddrive. I'll report back.
*sigh* I did not save the functional sourcess or ISO. :-/ But I found out something funny: The ASMS-Error happens somewhere at T-39. When I reboot and insert any other functional build the Installation finishes successfully!
So it's something on the CD but nothing that has already been copied to the harddrive.
------------------
I did the test:
A different harddrive + new CD-RW => ASMS-Error. :-(
------------------
Edit2:
I'll move everything to my laptop and try to run HFSLIP there. I have an idea what may be the reason for the problem. I'll report back in approximately 12 to 14 hours.
------------------
Edit3:
I did several new HFSLIP runs but all failed.
At first I tried to disable background tasks (Virus scanner, ZoneAlarm, etc) on my main System and ran HFSLIP. The ASMS-Error occured.
Then I moved the whole HFSLIP folder to my Notebook and started a new build with identical setting there. The ASMS-Error occured as well.
Now I removed the newest two patches that I added (rootsupd... and KB936357) and the branding.cab and tried a new build: Once again the ASMS-Error.
Du you still have HFSLIP v70506 (or any pre-1.5.0) anywhere? A build with that version does work but I don't have it anymore.
0 -
The ASMS-ERROR is back!
I build a new ISO with some additional drivers, the new roots-update and the new Intel-CPU patch and the ASMS-Error is back again.
---------------
Edit: For the next try I'll install a secondary IDE harddrive and move the HFSLIP-folder there.
I may also try to use a different CD-RW. That one that I still use has been rewritten quite often during all these tests.
0 -
Nope, same outcome
I can't see a reason why this should help but: Did you try the latest beta release as well?
0 -
The modified IE7 installer that is placed in I386\SVCPACK is a quiet installer (using /quiet switch) as opposed to the first GUI logon installer (using /passive switch). I suppose you waited a while after double-clicking IE7_INST.EXE to make sure it's installed, and then rebooted.
Can you expand IE7_INST.EXE and show what's inside SETUP.CMD?
I waited but nothing happend. I rebooted the system because I expected IE7 to be installed in the background but after the reboot IE7 was still missing.
I'll expand it and attach the setup.cmd on Saturday or Sunday.
-------------------
Edit:
Here we go...
@ECHO OFF
IF EXIST %SYSTEMROOT%\SYSTEM32\CMDOW.EXE CMDOW @ /HID
MD update
EXPAND UPDATE.CAB -F:* update >NUL
update\iesetup.exe /quiet /norestart /update-no /nobackup
EXIT0 -
Double-Posting, but worth it:
Our network share has a hyphen in its name that cannot be removed. It's caused by the software to install systems with PXE over the network...Might this be the Problem?
0 -
I moved the whole HFSLIP folder from \WIN-CD\HFSLIP to \HFSLIP.
I also added ALL patches, WMP11, IE7 and all cabs. I adjusted the afanswer.ini to install IE7 at T-13, drivercomp=A...
NO ASMS-ERROR
BUT: IE7 is not integrated. During the setup the IE7 installer has been started but after the installation there is only IE6. I also tried to start the IE7-installer exe from the i386\svcpack manually but it did not install IE7. It opens a dos box, does something for a few seconds and disappears.
0 -
New build: :-( ASMS-Error.
I'll do some strange builds just for testing purposes... something like: "only IE7" ... "IE7 + WMP11" ... "some but not all patches" etc.
*g* *sigh* Why can't this just work on my System? I need that system soon but want to have it installed this way.
----
I tried to integrate IE7, IE-patches, dotnet2 and WindowsUpdateAgent30.
Files in your HF folder:
IE7-KB929969-WindowsXP-x86-deu.exe
IE7-WindowsXP-KB933566-x86-DEU.exe
IE7-WindowsXP-x86-deu.exe
WindowsUpdateAgent30-x86.exe
Files in your HFCABS folder:
iuctl.cab
MUWEB_SITE.CAB
Files in your HFSVCPACK folder:
dotnet2.exeIt failed.
Tomorrow I'll try it without IE7. I hope that it is one of these (maybe dotnet2.exe?) that causes the error. If I can find the reason we may be able to solve it. I'll keep you up to date.
-------------------------
EDIT:
I tried the same updates + 928255 and IE7SLIPSTREAM=1 (instead of IE7SVCPACK=1), just to get sure that it is not the way how I integrate IE7. The installation failed as ususal (ASMS....).
Next build is already running: Removed IE7 and 928255 that was just added for the IE7SLIPSTREAM-test. Still remaining: dotnet2.exe from Ryan and Windows Update Agent 3.0. If this build fails I'll remove dotnet2.exe. Somehow I feel that it might be the dotnet2.exe.
-------------------------
EDIT2:
No IE7 but dotnet2.exe and Windows Update Agent => ASMS-error
Next: Without dotnet2.exe; Windows Update Agent 3.0 only.
If this will work I'll add everything except dotnet2.exe. If it fails I'll remove the WinUpdateAgent3.0 and add IE.
0 -
I made an offer to get a chance for at least a one-time-payment but Tomcat76 refused it.
Our company can not make any "donations". We would need some kind of service quote for "adjustments for enterprise use". If it would be accepted it might be payed. I can't guarantee it.
BTW: During the last weeks I am doing lots of testing for your project. As Tomcat said you don't have anyone else who tried to install from a network source.
0 -
CHKDSK /r on the partition that contains the HFSLIP folder: 0 errors.
I did a run with DRIVERCOMP=D and everything included: It FAILED! The same ASMS-error as before. So drivercomp=d did only seem to help because it was a "minimal" configuration that works with drivercomp=A as well.
0 -
You are talking about the "IE7 installer" so I guess you didn't slipstream it this time. INSTALL.INS from BRANDING.CAB should be inside IE7_INST.EXE in that case. Can you verify that it is?
I always try to integrate it at T-13 because of the png-issue.
BTW... Was this file created with IEAK7? I'm having a hard time believing that because of this:Wizard_Version=6.0.5730.1001
YES, it is! I was wondering about this version number as well because I expected to find something like 7.*
dotnet2.exeIf placed in HFSVCPACK, it should've been copied into SOURCESS\I386\SVCPACK just like before. The only difference is that the current test release initiates the install from SVCPACK.INF (just like in the old days) instead of from HFSLIP.CMD.
I just received the mail: dotnet2.exe is present in the right folder.
You know... I'm beginning to think that there are files that fail to copy on your computer. The first ASMS.CAB file you gave demonstrates a problem that's really puzzling me. But I can only say that for sure once you follow up on my last post in the other thread.Chkdsk /r is running.
Please don't mix things up! THIS thread is about the problems that I am facing in our company. It is independend from the other thread that is about the problems that I have at home. Nevertheless I doubt that my harddrive at home is defective. It is working pretty good without any issues until today. It's a 10k SCSI harddrive.
0 -
OK. I'm going to take a closer look at your list.
Meanwhile, can you tell me if the following three files exist in your original source (SOURCE folder)?
I386\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS\comctl32.dll
I386\ASMS\60\MSFT\WINDOWS\COMMON\CONTROLS\controls.cat
I386\ASMS\60\POLICY\60\COMCTL\comctl.cat
The files are there but with an underscore at the end:
comctl32.dl_
controls.ca_
comctl.ca_
(they are also available in SOURCESS)
----------
Attached: DRVINDEX.INF files from SOURCE and from SOURCESS.
-------------------
Edit: I'll do a new build with DRIVERCOMP=D but without any other changes...
0 -
I did it and it failed. The ASMS-folder-error again.
What I did:
HF: All needed patches until today (removed the replaced patches and I removed KB923191 as you said), IE7, WMP11.
HFCABS: BRANDING.CAB, IEAWSDC.cab, iuctl.cab, MuCatalogWebControl.cab, MUWEB_SITE.CAB (I downloaded it today and it is a little bit larger than the file I used until now.), OGAControl.cab, OPUC4.cab.
HFSVCPACK: dotnet2.exe
HFTOOLS: I changed the hfanswers.inf to IE7SVCPACK=1
Attachment: HFSLIP.log as RAR file.
What should I do next?
0 -
It does not seem to copy any content OR it fails.
Attached branding.cab. That's the one that has failed every time.
Today I created a new one that I don't have right now and that I did not test yet. The new one is on the test-system in our company and it is a little bit different. I tried to keep it simple.
IEAK creates a setup.exe to force the branding on an already existing installation. I tried it on a test system and it worked pretty good that way.
----------------
dotnet2.exe: I'll tell someone to check it or we would have to wait until Friday..
0 -
No error messages but dotnet2 is not integrated.
The file dotnet2.exe is located in: HFSLIP\HFSVCPACK.
Is this still correct or should it be placed in HFSLIP\HF?
Less important: The branding.cab does not work. It seems to be ignored.
EDIT: The branding.cab inside the IE7 installer seems to be damaged! I tried to extract it with 7zip but got an error message. The Branding.cab that I added into the HFCABS folder is OK. Can you check that?
EDIT2: The file is just empty. That's why I get an error message when I select "extract files".
0 -
This is driving me nuts.
The installation works! No ASMS-error anymore.
What should I try next?
0 -
Sorry... too many tests.
I'll prepare the "minimal setup" files and post the ASMS.CAB.
So the next run does not inculde any patches, no IE7, no dotnet and no WMP11. Branding.cab is removed and HFANSWERES.INI is corrected to "IE7SVCPACK=" (instead of "IE7SVCPACK=1" with IE7) and DRIVERCOMP=A.
Nevertheless the installation worked with drivercomp=d.
---------------------------
EDIT: The results...
ASMS folders are equal in size, number of files and number of folders. They are identical. The ASMS.cab contains just an empty txt-file (see attachment). I also added the hfslip.log and the HFANSWERS.INI. Just to confirm the errors mentioned above I'll try to install from this source.
0 -
DRIVERCOMP=D works! No ASMS-Error-Message!
But IE7 is not integrated. *sigh* Still IE6.
---------
Three cabs: iuctl.cab, muweb_site.cab and branding.cab (ok, the last one is almost empty...)
ASMS.CAB attached.
0 -
Hi!
No, the ASMS in SOURCESS is bigger.
SOURCE\i386\ASMS:
54 files, 60 folders, 7.761.210 Bytes
SOURCESS\i386\ASMS:
65 files, 63 folders, 11.339.921 Bytes
I'll try a drivercomp=D later...
0 -
The files are attached. I'll try an installation with a PATA IDE drive just to check if this is causing the problems.
------------------
Edit: Using the same CD did not change anything when I tried to install on the PATA-drive. Then I used an older CD that has been created with HFSLIP 70506: It worked but IE was not integrated as it should have been. No I am building a new CD with the brand new test release. I'll report back.
0 -
@ZEDOX:
A little bit offtopic but where can I get the (up-to-date) OPUC.DLL? I tried to google for it but the links to the Microsoft website that could help were dead. Is it part of a special patch? If so, please tell me the KB-#...
Thanks!
0 -
Hmmmm... Sorry but I did not check if the roots or .net installed. *doh*
You can show mapped drives with "net use". I know that it's not very nice but once I handled such output by writing it into a .txt-file and then filtering it with "sed".
0 -
The SATA-drivers are manually integrated. I have a $OEM$ folder with several subfolders that contain the SI3114 drivers and a file named si3114.sys is located in the I386 directory. Some lines are added in the txtsetup.sif as well.
That's all that is changed compared to the original WinXP SP2 CD.
0 -
Hello!
I have the exact same problem that sgt Stryder has when I try to install WinXP from CD on my dual Opteron based machine. In German it looks like this:
Fehler:
Installation Failed : D:\I386\asms. Error Message: Unzulässige Funktion.
***
Schwerwiegender Fehler:
Eine der für die Installation benötigten Komponenten konnte nicht installiert werden.
Unzulässige Funktion.
***This does not happen when I try to install from a network source in our company (completely different hardware and no installation from CD).
I already tried to remove ALL updates, WMP11, IE7 and the winnt.sif but it does not change anything.
Attached two HFSLIP.log files in one ZIP: One with "nothing" integrated and one with WMP11, IE7 and patches. Both "integrations" cause the same error.
Maybe this might help: Compared to the source I use in our company I already added a SATA driver (SI3114.sys). This is a "known good" driver integration that I used several times. I also tried to do a test installation with this original WinXP SP2 source + Si3114 driver and it worked perfect.
After I used this source with HFSLIP it failed with the errormessage from above.
0
Our network share has a hyphen in its name that cannot be removed. It's caused by the software to install systems with PXE over the network...
I'm having trouble with HFSLIP 1.5
in HFSLIP
Posted
Actually I burned the whole HFSLIP-folder to a DVD and use it from the very first try. But I started my builds @home with 1.5.0. I just have an "older" build with v70506 that I finished in our company.
Don't lough but right now I did a strange "trick" to force the installation to pass the ASMS-Error:
I used the latest build you can see in the newest log file and waited for the ASMS-error. Then I replaced the installation CD with the older (v70506) build and rebooted. The setup continued at that position. Right after the CD-access I replaced the CD again with the fresh build.
Result: IE7 is integrated (REALLY integrated!) not installed at T-13 with SVCPACK, that did not work doing it this way, WMP11 is integrated, patches seem to be integrated (have to check it), ... My "branding.cab" did not work. In our company I just gave up to use the branding.cab-file and added all needed information to a REG-file that does the trick perfect. I'll try the same here later (low priority because I use Firefox all the time).
So far so good - but at the first boot I get an error message that says something weired about "msoobe.exe". Low Priority because it may be ASMS-error-related as well. The ASMS has to be fixed first.
The one working build (when I thought that it was the hyphen in the folder) was made from the same source and the same patches. I already tested that anyone of the patches is enough to cause the ASMS-error to appear. I am a little bit helpless right now.
Next to try: I'll use the 1.4.5 and/or the test release and report back... Tomorrow... Have to get some sleep now.