StarWind iSCSI SAN
StarWind Native SAN for Hyper-V
 

Windows Repair

Initiator (iSCSI, FCoE, AoE, iSER and NVMe over Fabrics)

Moderators: art (staff), anton (staff), Anatoly (staff), Max (staff)

Windows Repair

Postby Tgellan » Fri Oct 29, 2004 8:11 am

Hi,

Just encountered the following problem while repairing a WinXP SP1:

Blue Screen (only background) and message telling that starport.dll could not be found, therefor impossible to repair the system!!!!

Happily it was possible to go back to system, remove Starport, then it worked. But still I think this should not be!?

Just my 5 cents
Tgellan
Tgellan
 
Posts: 3
Joined: Fri Sep 17, 2004 3:25 pm

Re: Windows Repair

Postby anton (staff) » Fri Oct 29, 2004 4:32 pm

Actually there's no single file called StarPort.dll in our distribution. However we just can guess it was broken driver installation sequence. Never heard about this one before :-( Did you perform installation under Administrator account? Can we ask you to send us installation log (I'm afraid you'll have to install StarPort once again to catch the problem...). Sorry for misfortunes and thanks for help! :-)

Tgellan wrote:Hi,

Just encountered the following problem while repairing a WinXP SP1:

Blue Screen (only background) and message telling that starport.dll could not be found, therefor impossible to repair the system!!!!

Happily it was possible to go back to system, remove Starport, then it worked. But still I think this should not be!?

Just my 5 cents
Tgellan
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
User avatar
anton (staff)
Site Admin
 
Posts: 3922
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands

Postby Tgellan » Sat Oct 30, 2004 1:43 pm

Sorry, that won┤t be possible as that specific machine has been reinstalled in meantime from scratch... :-(

The name of the dll was from memory, but it is shure that it was named something like starport, and after uninstall it just worked fine.?

It┤s been a first time for me to do a repair installation, and I won┤t do it just for testings, sorry...

But it should be easy enough to test if it┤s a "normal" problem -> just take a test machine and do that repair stuff from M$... If it works just fine, should have been related to other problems and it has just be bad luck that it conflicted with your software (which is by the way just great)

Thanks
Tgellan
Tgellan
 
Posts: 3
Joined: Fri Sep 17, 2004 3:25 pm

Postby anton (staff) » Sat Oct 30, 2004 1:57 pm

We're not able to reproduce the problem here :-( It's a pity you do not have test machine with original configuration any more. Seems we'll have to take another chance to sort this issue out. When somebody else (I really hope it would be someone from our testers) would catch the problem again. Sorry for not beeing helpful this time!

Tgellan wrote:Sorry, that won┤t be possible as that specific machine has been reinstalled in meantime from scratch... :-(

The name of the dll was from memory, but it is shure that it was named something like starport, and after uninstall it just worked fine.?

It┤s been a first time for me to do a repair installation, and I won┤t do it just for testings, sorry...

But it should be easy enough to test if it┤s a "normal" problem -> just take a test machine and do that repair stuff from M$... If it works just fine, should have been related to other problems and it has just be bad luck that it conflicted with your software (which is by the way just great)

Thanks
Tgellan
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
User avatar
anton (staff)
Site Admin
 
Posts: 3922
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands


Return to StarPort

Who is online

Users browsing this forum: No registered users and 2 guests