Jump to content

"bitstransfer.format.ps1xml" copy error


bynkook
 Share

Recommended Posts


This file sounds strange to me. I think you are trying to slipstream something that you are not supposed to. Please double check your hotfixes against mimo's or muppet hunters lists and delete the offending hotfix(s).

Link to comment
Share on other sites

hi bynkook! pls see my old post ... try taking out WindowsXP-KB968930-x86-KOR.exe ... see if it helps ... ;)

link corrected ... thanks for poining it out bphlpt ... i linked it locally to the image posted by bynkook.

Edited by Kiki Burgh
Link to comment
Share on other sites

yes, the "WindowsXP-KB968930-x86.." was the culprit.

Only thing i've done is just removing 968930 from /HF folder

and I dont see any error message now.

I think HFSLIP has some problem with 968930 hotfix.

Thanks!!!!!

Link to comment
Share on other sites

I've had the same problem too; I suspect it's due to the filenames having extensions of >3 characters, but I could be wrong. All I know is that all the *.ps1xml files are failing.

I'm in the process of running a test where I put that hotfix into HFSVCPACK_SW1 instead of HF to see if it installs it. However my EeePC isn't exactly the fastest machine around, so it takes a while to test the install :)

Link to comment
Share on other sites

hi! these are the likely offending files in:

WindowsXP-KB968930-x86-ENG.exe

Windows Management Framework Core package (Windows PowerShell 2.0 and WinRM 2.0) (KB968930):

[font="Courier New"]\HF\968930\bitstransfer.psd1
\HF\968930\importallmodules.psd1
\HF\968930\bitstransfer.format.ps1xml
\HF\968930\certificate.format.ps1xml
\HF\968930\diagnostics.format.ps1xml
\HF\968930\dotnettypes.format.ps1xml
\HF\968930\filesystem.format.ps1xml
\HF\968930\getevent.types.ps1xml
\HF\968930\help.format.ps1xml
\HF\968930\powershellcore.format.ps1xml
\HF\968930\powershelltrace.format.ps1xml
\HF\968930\registry.format.ps1xml
\HF\968930\types.ps1xml
\HF\968930\wsman.format.ps1xml[/font]

the only others having the same files (but not as many as above, only this: powershelltrace.format.ps1xml) are:

WindowsXP-KB926139-v2-x86-ENU.exe

Windows PowerShell 1.0 English-Language Installation Package for Windows XP (KB926139) &

Windows PowerShell 1.0 Localized Installation Package for Windows XP (KB926140)

Windows PowerShell 1.0 Multilingual User Interface Package for Windows XP (KB926141)

... in my previous build though using hfslip-1.5.0 (last 071607), powershell 1.0 was installed correctly with shortcuts visible in the start menu ... could be worth a look how this kind of files should be handled ... cheers!

checked on the following updates too (just for possibilities) but no similar files exist:

msxml4-KB973685-enu.exe

Description of an update for Microsoft XML Core Services 4.0 Service Pack 3

msxml4-KB973686-enu.exe

Description of an update for Microsoft MSXML Core Services 6.0 Service Pack 2

WindowsXP-KB973687-x86-ENU.exe

Description of updates for Microsoft MSXML Core Services 3.0 and MSXML Core Services 6.0

WindowsXP-KB969084-x86-enu.exe

Description of the Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3, Windows Vista SP1, and Windows Vista SP2

* here's a background about_Format.ps1xml

SHORT DESCRIPTION

The Format.ps1xml files in Windows PowerShell define the default display

of objects in the Windows PowerShell console. You can create your own

Format.ps1xml files to change the display of objects or to define default

displays for new object types that you create in Windows PowerShell.

nb: removed urls as i got this prompt:

You have entered a link to a website that the administrator does not allow links to
upon submission of this post ... just do a quick search fr ms website. ;)

hmm ... strange, i tried it again & it got through ... :blink:

Edited by Kiki Burgh
Link to comment
Share on other sites

I've had the same problem too; I suspect it's due to the filenames having extensions of >3 characters, but I could be wrong. All I know is that all the *.ps1xml files are failing.

I'm in the process of running a test where I put that hotfix into HFSVCPACK_SW1 instead of HF to see if it installs it. However my EeePC isn't exactly the fastest machine around, so it takes a while to test the install :)

Tried but failed :(

only way I could get it to install correctly was to make a switchless installer and put it in HFGUIRUNONCE

Link to comment
Share on other sites

I think tommyp and mimo should consider this problem quickly.
May way to consider this problem is that I will put the info in HFSLIP file-checker that KB968930 is not compatible with the current HFSLIP :)

Regards, Mimo

Edited by Mim0
Link to comment
Share on other sites

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
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...