Jump to content

SWFLASH.cab spoils XPcreated installation


Recommended Posts

Posted

First of all, Hello Everybody and thank you

especially to our patron here, GM :)

Just a little report after my 30 setups in 6 days. :D

I WONT post my xpcreate log by now cause I'm working on something else right now, but I will if GM thinks it's really interesting.

Making it short: dloaded almost all Hotfixes here; put them in the right folders following GM's site indications; my setups works fine except that netorking doesn't work at start: workstation and dhcp client services are off and if I started (net works) next reboot are off again.

Made a binary search (well not at start) to find WICH f**g patch was that that was rotting my setup and found that was swflash.cab! :rolleyes: The most innocuos in my thought.

The problem is that I don't know what version I have: I googled the file name and dloaded the first I found on shockwave domain.

I think that a link to a valid, trustable cab would be good.

Thank you

see on the other post

Cyberchicken (who forgot to write a signature)


Posted

SWFLASH.CAB should be 483,750 Bytes. It is linked to all over the Internet, and in any web page that uses Flash. The version number is listed in the .INF file inside the .CAB.

Posted

Hmmm :) the size is right and the version inside the .inf is

VersionNumber = "7,0,19,0"

Very strange, isn't it?

Then in the next days I'm gonna get the latest xpcreate, have a good log and show you exactly just what happens.

Forgot to mention tha I'm using xp pro, main sp is sp1-non-a and test rig is on vmware

thank you

yawn :rolleyes: good night

Posted

****

I ran xpcreate adding swflash.cab and I had an error

-- 14.49.40 --> Setting up Run-Time Variables.-- 14.49.40 --> Listing Hotfixes and Updates-- 14.49.40 --> Removing Previous Creation directories.-- 14.50.13 --> Removing TEMP Files.-- 14.50.13 --> Creating TEMP directories.-- 14.50.13 --> Start copying files.-- 14.52.25 --> Determine Source Version.-- 14.52.26 --> Found Source Version: XPP-- 14.52.26 --> Found Minor Version: 1-- 14.52.26 --> Found Service Pack Version: 0-- 14.52.26 --> Found Language Version: ENU-- 14.52.26 --> Slipstreaming Service Pack.-- 14.52.26 --> Extracting Service Pack : xpsp1_en_x86.exe-- 14.52.57 --> Merging Service Pack : xpsp1_en_x86.exe-- 14.53.35 --> Copying Hotfixes: Type 1-- 14.53.35 --> Extracting for sort order.-- 14.54.08 --> Sort Hotfixes ...-- 14.54.09 --> Copying Hotfixes: Type 2-- 14.54.09 --> Copying SVCPACK Executables-- 14.54.09 --> Repack all the Special Case Type II Hotfixes-- 14.54.10 --> Slipstreaming MDAC update.-- 14.54.28 --> Repackaging any MSI installers.-- 14.54.28 --> Repacking dotnetfx.exe-- 14.55.48 --> Updating Macromedia Flash.-- 14.55.50 --> Merging Hotfixes.-- 14.56.04 --> Creating Command File to extract Hotfixes.-- 14.56.04 --> Launching Hotfix Extraction script.-- 14.56.55 --> Saving the CAT files.-- 14.56.56 --> All Hotfixes extracted: Clean out the junk files.-- 14.56.56 --> Expanding the CABS. This will take a moment.-- 14.56.56 --> Expanding: dajava.cab-- 14.56.57 --> Expanding: DRIVER.CAB-- 14.58.27 --> Expanding: FP40EXT.CAB-- 14.58.29 --> Expanding: hscmui.cab-- 14.58.29 --> Expanding: hscxpsp1.cab-- 14.58.30 --> Expanding: IIS6.CAB-- 14.58.42 --> Expanding: IMS.CAB-- 14.58.43 --> Expanding: MANAGER.CAB-- 14.58.44 --> Expanding: MMSSETUP.CAB-- 14.58.44 --> Expanding: MODEM.CAB-- 14.58.45 --> Expanding: OSC.CAB-- 14.58.45 --> Expanding: sp1.cab-- 14.58.52 --> Expanding: WIN.CAB-- 14.58.52 --> Expanding: WINSYS.CAB-- 14.58.52 --> Expanding: WINSYS32.CAB-- 14.58.52 --> Expanding: xmldso.cab-- 14.58.52 --> Find out which files come from CABs.-- 14.58.53 --> Get everything from DRIVER.CAB.-- 15.00.36 --> Copy SP1.CAB.-- 15.00.47 --> Update the DRIVER and SPx CABS.-- 15.00.50 --> Adding new CAB files if needed.-- 15.00.53 --> CAB DAJAVA Does NOT need RePacking-- 15.00.54 --> RePacking CAB: DRIVER. Patience please.-- 15.10.57 --> CAB FP40EXT Does NOT need RePacking-- 15.10.57 --> CAB HSCMUI Does NOT need RePacking-- 15.10.58 --> CAB HSCXPSP1 Does NOT need RePacking-- 15.10.59 --> CAB IIS6 Does NOT need RePacking-- 15.10.59 --> CAB IMS Does NOT need RePacking-- 15.10.59 --> CAB MANAGER Does NOT need RePacking-- 15.10.59 --> CAB MMSSETUP Does NOT need RePacking-- 15.10.59 --> CAB MODEM Does NOT need RePacking-- 15.10.59 --> CAB OSC Does NOT need RePacking-- 15.10.59 --> RePacking CAB: SP1. Patience please.-- 15.11.48 --> CAB WIN Does NOT need RePacking-- 15.11.48 --> CAB WINSYS Does NOT need RePacking-- 15.11.49 --> CAB WINSYS32 Does NOT need RePacking-- 15.11.49 --> CAB XMLDSO Does NOT need RePacking-- 15.11.49 --> Update the DOSNET.INF file-- 15.11.49 --> Figure out which files are new ...-- 15.12.00 --> Files in CABs are not new.-- 15.13.13 --> Files in I386 are not new.-- 15.13.14 --> Add list of New Files to [Files] in DOSNET.INF.-- 15.13.14 --> RoyalBox's SVCPACK.INF Creator-- 15.13.14 --> Adding SATA/RAID support.-- 15.13.14 --> Update uncompressed versions.-- 15.13.14 --> ntdll.dll Found in both WORKDIR and I386.-- 15.13.14 --> ntdll.dll Found in both WORKDIR and I386\SYSTEM32.-- 15.13.14 --> xmldso.cab Found in both WORKDIR and I386.-- 15.13.14 --> Compressing all the hotfix Files.-- 15.15.21 --> Put all the files for the CD togetherFailure renaming "C:\Jobs\THE BOOTDISK\XPCREATE\CDROOT\I386\ASMS\10100\MSFT\Windows".ERROR 32: The process cannot access the file because it is being used by another process.Failure renaming "C:\Jobs\THE BOOTDISK\XPCREATE\CDROOT\I386\ASMS\60100\policy".ERROR 32: The process cannot access the file because it is being used by another process.-- 15.17.10 --> Create an ISO image-- 15.21.32 --> Burning ISO image
     All Done Press Enter.

Note tha it made the iso even if I had set doiso=no

I attach the corresponding xpcreate log

I'm going to try with the new xpcreate and repost

XPCREATE.LOG

XPCREATE.LOG

Posted

I don't really see how that error is related to SWFLASH.CAB, or even XPCREATE. Why does someone have that file locked? Note that anti-virus programs can cause undesired results when trying to keep up with XPCREATE file creation.

Eliminate the white space in DOISO = NO in your XPCREATE.INI file, and you should be OK.

Posted
Eliminate the white space in DOISO = NO in your XPCREATE.INI file, and you should be OK.
s**t! I'm very dumb, :rolleyes: I slept too little :)

Anyway, I made the rerun with 24-apr xpc

I attach the logs. I'll tell you tonight when install is finished and I'm back home.

I don't really see how that error is related to SWFLASH.CAB, or even XPCREATE. Why does someone have that file locked?

I wonder the same

Note that anti-virus programs can cause undesired results when trying to keep up with XPCREATE file creation.

hmmm very interesting. I have the AVG. I'll try to switch it off the next test.

-- 15.30.41 --> Setting up Run-Time Variables.

-- 15.30.41 --> Listing Hotfixes and Updates

-- 15.30.42 --> Removing Previous Creation Directories.

-- 15.30.43 --> Removing TEMP Files.

-- 15.30.48 --> Creating TEMP directories.

-- 15.30.48 --> Start copying files.

-- 15.32.34 --> Determine Source Version.

-- 15.32.34 --> Found Source Version: XPP

-- 15.32.34 --> Found Minor Version: 1

-- 15.32.34 --> Found Service Pack Version: 0

-- 15.32.34 --> Found Language Version: ENU

-- 15.32.34 --> Slipstreaming Service Pack.

-- 15.32.34 --> Extracting Service Pack : xpsp1_en_x86.exe

-- 15.33.00 --> Merging Service Pack : xpsp1_en_x86.exe

-- 15.33.15 --> Copying Hotfixes: Type 1

-- 15.33.15 --> Extracting for sort order.

-- 15.33.46 --> Sort Hotfixes ...

-- 15.33.46 --> Copying Hotfixes: Type 2

-- 15.33.49 --> Copying SVCPACK Executables

-- 15.33.49 --> Repack all the Special Case Type II Hotfixes

-- 15.33.49 --> Slipstreaming MDAC update.

-- 15.34.06 --> Repacking any MSI installers.

-- 15.34.06 --> Repacking dotnetfx.exe

-- 15.35.19 --> Updating Macromedia Flash.

-- 15.35.21 --> Merging Hotfixes.

-- 15.35.31 --> Creating Command File to extract Hotfixes.

-- 15.35.36 --> Launching Hotfix Extraction Script.

-- 15.36.37 --> Saving the CAT files.

-- 15.36.37 --> All Hotfixes extracted: Clean out the junk files.

-- 15.36.37 --> Expanding the CABS. This will take a moment.

-- 15.36.37 --> Expanding: dajava.cab

-- 15.36.38 --> Expanding: DRIVER.CAB

-- 15.37.56 --> Expanding: FP40EXT.CAB

-- 15.37.58 --> Expanding: hscmui.cab

-- 15.37.58 --> Expanding: hscxpsp1.cab

-- 15.37.58 --> Expanding: IIS6.CAB

-- 15.38.09 --> Expanding: IMS.CAB

-- 15.38.10 --> Expanding: MANAGER.CAB

-- 15.38.10 --> Expanding: MMSSETUP.CAB

-- 15.38.10 --> Expanding: MODEM.CAB

-- 15.38.11 --> Expanding: OSC.CAB

-- 15.38.11 --> Expanding: sp1.cab

-- 15.38.15 --> Expanding: WIN.CAB

-- 15.38.15 --> Expanding: WINSYS.CAB

-- 15.38.15 --> Expanding: WINSYS32.CAB

-- 15.38.15 --> Expanding: xmldso.cab

-- 15.38.15 --> Find out which files come from CABs.

-- 15.38.15 --> Get everything from DRIVER.CAB.

-- 15.38.59 --> Copy SP1.CAB.

-- 15.39.06 --> Update the DRIVER and SPx CABS.

-- 15.39.07 --> Adding new CAB files if needed.

-- 15.39.14 --> CAB DAJAVA Does NOT need Repacking

-- 15.39.14 --> Repacking CAB: DRIVER. Patience please.

-- 15.48.01 --> CAB FP40EXT Does NOT need Repacking

-- 15.48.01 --> CAB HSCMUI Does NOT need Repacking

-- 15.48.01 --> CAB HSCXPSP1 Does NOT need Repacking

-- 15.48.02 --> CAB IIS6 Does NOT need Repacking

-- 15.48.02 --> CAB IMS Does NOT need Repacking

-- 15.48.02 --> CAB MANAGER Does NOT need Repacking

-- 15.48.02 --> CAB MMSSETUP Does NOT need Repacking

-- 15.48.02 --> CAB MODEM Does NOT need Repacking

-- 15.48.02 --> CAB OSC Does NOT need Repacking

-- 15.48.02 --> Repacking CAB: SP1. Patience please.

-- 15.48.49 --> CAB WIN Does NOT need Repacking

-- 15.48.49 --> CAB WINSYS Does NOT need Repacking

-- 15.48.49 --> CAB WINSYS32 Does NOT need Repacking

-- 15.48.49 --> CAB XMLDSO Does NOT need Repacking

-- 15.48.49 --> Update the DOSNET.INF file

-- 15.48.49 --> Figure out which files are new ...

-- 15.49.17 --> Files already in CABs are not new.

-- 15.50.32 --> Files already in I386 are not new.

-- 15.50.33 --> Add list of New Files to [Files] in DOSNET.INF.

-- 15.50.33 --> RoyalBox's SVCPACK.INF Creator

-- 15.50.34 --> Adding SATA/RAID support.

-- 15.50.34 --> Looking for SATA drivers.

File Not Found

-- 15.50.34 --> No SATA drivers found.

-- 15.50.34 --> Update uncompressed versions.

-- 15.50.34 --> ntdll.dll Found in both WORKDIR and I386.

-- 15.50.34 --> ntdll.dll Found in both WORKDIR and I386\SYSTEM32.

-- 15.50.34 --> xmldso.cab Found in both WORKDIR and I386.

-- 15.50.34 --> Compressing all the hotfix Files.

-- 15.52.33 --> Put all the files for the CD together

-- 15.54.36 --> Create an ISO image

-- 15.59.10 --> Burning ISO image

    All Done Press Enter.

XPCREATE.LOG

XPCREATE.LOG

Posted

you don't neccesarily have to post the output in the DOS prompt.....

the relevant stuff is in the log file, not the window.

I've had no problems with the services, but then again, in my install I ahve a reg file that starts and stops ones I want, so I never have the default running.

Posted

Hi

I've had the exactly same problem with one of my last unettended CD I've made, but I used webmedic's script (the old one) without the Flash stuff. Since I couldn't find the cause of the problem I tried XPCREATE, and it works again without any problems, the services are starting up as usual. I don't think the problem is related to the Flash stuff, since I havn't included it before with the old script, it must be something else, maybe one of the newer patches or so.

Posted

Personally, I vote for the "fluke": error with neither reason nor rhyme.

This time, the DOS window was relevant: there should never be any lines not starting with a Time Stamp. "File Not Found", though not a "hard" error that will cause problems, is a logical error. Fixed.

Posted

YES! I recreated the conditions by which swflash.cab ruins my installation.

But first some replies

@Alanoll

you don't neccesarily have to post the output in the DOS prompt.....
I knewn It, but somehow I found those errors strange...
I've had no problems with the services, but then again, in my install I ahve a reg file that starts and stops ones I want, so I never have the default running.

It's not that simple beacause If I start the right services (workstation and dhcp at least), next reboot are off again.

@mr_shaba

I used webmedic's script (the old one) without the Flash stuff. Since I couldn't find the cause of the problem I tried XPCREATE, and it works again without any problems, the services are starting up as usual. I don't think the problem is related to the Flash stuff, since I havn't included it before with the old script, it must be something else, maybe one of the newer patches or so.

If you say so then it could be some interaction between one of the patches and the way swflash.cab is slipstreames. Hav you dropped any patch between webmedic's script and xpcreate?

Anyway for me is like that: I don't need shwflash and I need all other patches, so I'll drop the first.

To GM the task to understand what's going on.

As I was said I reproduced the malfunctioning. (I remind I'm using vmWare 3)

Had to rerun xpc since last one some how missed a file (pdbbccp32.dl_).

The printed report is the same, with "file not found" right after "looking for sata drivers".

I attache the xpc log

The simptoms are: the network at first logon is not working (while without swflash I can immediately communicate with my other machines); Workastation and DHCP_client are off (Automatic, not started); if I start them at the next reboot they're again stopped.

Thank you

Bye

XPCREATE.LOG

XPCREATE.LOG

Posted

I have trouble believing the FLASH update itself causes any of these problems, but if getting rid of it solves the issue ... get rid of it by all means. It is just a little "extra frill" added at no cost, and I won't be digging into it at this time. Sorry.

I see you are not using the VERY latest and greatest XPCREATE. Please see the Sticky Topic at the top off the forum: it is the only version I will look at the logs from.

Thanks for reporting thre "File not found" error: this should be gone in the new version.

An instersting comparison would be of the two CDs you created: one with FLASH, one without. Next step would be in creating a simple XPCREATION, using the failsafe list, and ZERO files in FILESCD, not even WINNT.SIF, and see if the problem persists. Perhaps it is an interaction with one of your CUSTOM files and FLASH?

Posted
I have trouble believing the FLASH update itself causes any of these problems, but if getting rid of it solves the issue ... get rid of it by all means. It is just a little "extra frill" added at no cost, and I won't be digging into it at this time. Sorry.
Don't be sorry!
I see you are not using the VERY latest and greatest XPCREATE.

Geez! You're too fast man! Anyway I ran that setup BEfore Apr 29 2004, 01:48 AM :D I can't use your code before you publish it! :)

Hey, you told me that were 6 weeks to wait before the new version! You pulled my leg :rolleyes:

Thanks for reporting thre "File not found" error: this should be gone in the new version.
I hade many of them in the various situations I tried, but have no logs.

I'll tell you if I see them if you're keen on eliminating glitches.

An instersting comparison would be of the two CDs you created: one with FLASH, one without.

Is that a comparison I can mail you? In this very moment I have the two isos you said.

Next step would be in creating a simple XPCREATION, using the failsafe list, and ZERO files in FILESCD, not even WINNT.SIF, and see if the problem persists.
I'm NOT going to make a manual setup!
Perhaps it is an interaction with one of your CUSTOM files and FLASH?

Don't think so: I have no custom files except some test bacthes i run from the various unattended run point (they're basically hello world with time stamp), and obviously an unattend.txt ran from command line.

I think to remember, but I'm not sure, that the problem with the network disappears if I remove sp1 from the slipstreaming (leaving all the others and shwflash).

bye

Posted

I still believe it is operator error ... There is something in one of your files that does not jive. Anyway, unless someone else has the same thing, I'm not going to look into it right now.

The reason for the new release was that I noticed that the log files were getting too large for posting. I needed to fix that. The other modifications came along for the ride. I certainly don't see any updates in the near future.

Still, you have something working, and that is the bottom line.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...