Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
zedox

Cannot Export SSIP1.TXT: Error Opening File.

Recommended Posts

I'm getting this error when installing...

Cannot Export SSIP1.TXT: Error Opening File.

Any ideas?

I've attached my log.

HFSLIP.TXT

Share this post


Link to post
Share on other sites

Do you have regedit.exe in the Windows folder of the newly installed source?

Please attach a zipped copy of SOURCESS\I386\SVCPACK\HFSLIP.CMD here (or copy and paste its content) so I can have a look at it.

Share this post


Link to post
Share on other sites

regedit.exe is present in the windows folder after install.

However, i'm sure its normally all caps?

I've attached a copy of my hfslip.cmd as a zip file.

HFSLIP.zip

Share this post


Link to post
Share on other sites
@ECHO OFF
CD %SYSTEMROOT%\HFSLIP
SET SSIP=Y
%SYSTEMROOT%\REGEDIT /S/E SSIP1.TXT "HKEY_LOCAL_MACHINE\SYSTEM\Setup"
TYPE SSIP1.TXT>SSIP2.TXT
FOR /F %%I IN ('FINDSTR/IR "SystemSetupInProgress.=dword:00000000" SSIP2.TXT') DO SET SSIP=N
IF "%SSIP%"=="Y" (
rundll32.exe advpack.dll,LaunchINFSection %SYSTEMROOT%\HFSLIP\HFSLPGUI.INF,HFSLIPGUI_Run
EXIT
)
IF EXIST %WINDIR%\SYSTEM32\dllcache\plugin.ocx DEL/Q/F %WINDIR%\SYSTEM32\dllcache\plugin.ocx
rundll32.exe advpack.dll,LaunchINFSection %WINDIR%\HFSLIP\HFSLPGUI.INF,HFSLIPGUI_Rem
EXIT

Share this post


Link to post
Share on other sites

This is getting really difficult. The only thing I can imagine going on is that the temporary WINDOWS\HFSLIP folder is removed or doesn't exist prior to execution of HFSLPGUI.CMD. This causes the "CD %SYSTEMROOT%\HFSLIP" (change directory) command to fail. The system should then be in a directory in which Windows (or Windows setup) doesn't allow you to write to, which causes the registry export to fail (and that's the error message you see).

Are you installing over a network? In a Virtual Machine? Does this also happen when installing from CD?

Share this post


Link to post
Share on other sites

I really don't know.

When did this start happening? Any particular version of HFSLIP?

Share this post


Link to post
Share on other sites

the latest version and the last beta.

It used to work fine, same goes for the windows media player 11 problem i'm having.

Can i download older versions anywhere?

Edited by zedox

Share this post


Link to post
Share on other sites

PLEASE IGNORE THIS POST

Edited by zedox

Share this post


Link to post
Share on other sites

Ok i've checked the HFSLIP folder during install using Shift-F10

The SSIP1.TXT file is not present in there.

But other files are.

Cheers

EDIT: I think I may have figured out whats going on. The CD %SYSTEMROOT%\HFSLIP command isnt taking not because the folder is not there but because cmd is stuck on the $OEM$ folder of the disc. (That was provided by DELL)

I've removed this folder now... and testing, have a feeling this may cure it.

Edited by zedox

Share this post


Link to post
Share on other sites

Thank you for your time tomcat76... It was the $OEM$ folder causing the problem. wonder if its causing the problems with Windows Media Player 11.

Thanks again.

Share this post


Link to post
Share on other sites

To clarify... SSIP1.TXT is not supposed to be on the CD or handled by Windows setup. It is created only when HFSLPGUI.CMD is executed (and deleted when the temporary HFSLIP folder is removed).

I'm only saying this in case you were looking for it on the CD or in the SOURCESS folder created by HFSLIP.

Share this post


Link to post
Share on other sites

This topic has some age on it.... but today, I got the same error while doing a CD install on a Dell 600M.... (I wonder if I'll get the error on a Dell Mini 9....?) Any way, I used Beta H for the integration & I just wondered:

Is this error serious & is it necessary to redo my CD/slip??

(I simply clicked OK.... There was a message in another command window that zipped by too quickly to see what it said. Other than that 1 error, the install seems like it went okay.)

Thanks for any help. :)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...