webOS Nation Forums >  webOS smartphones (Pre, Pixi, Veer) >  webOS tips, information, and resources > Blue Screen after SDK install 5 tries now.
Blue Screen after SDK install 5 tries now.

  Reply
 
LinkBack Thread Tools Display Modes
Old 07/16/2009, 09:03 PM   #1 (permalink)
Member
 
Join Date: Jun 2009
Posts: 40
Likes Received: 0
Thanks: 9
Thanked 2 Times in 2 Posts
Default Blue Screen after SDK install 5 tries now.

I have had a weird issue with SDK. I downloaded the leaked version and after the restart I got a BLUE SCREEN after the windows logo (it gets far enough to where windows is actually about to login).

So I ran windows repair and it didnt work. I tried many things, but no success. I just formatted the HDD. Well I installed again on a fresh copy of windows. The same thing happened.

So I stopped trying for a week, then I found the SDK from the link on this site... the same thing happened.

So I was just done... untill the official release came out today!!

I installed it with crossed fingers and what do you know... a BLUE SCREEN.


what do you all think.
This is really weird.. I have no problems with the computer otherwise.

-Tried 4 times on new copies of windows
-Tried SDK from the link on this site
-tried the official SDK
-I tried on fresh copy with only drivers that were needed (so no program issue)
-I also followed the directions to a T on the palmdev site. I installed the other progs first on the PALM Dev site on this last attempt today.

FIXED!!!
I took the advice of leebenjp

I used ubuntu though. ubuntu is just this bad *** free software that you can load an operating system from cd before installing if you want. I loaded the temp OS. Searched for MSVCRT.DLL found 3 in the windows folder. I renamed the one in the system 32 folder to MRVCRT.dllBAK and copied one of the other ones from some other folder (use windows search) into the sys32 folder..... and again I have fixed something without completely understanding what Im doing.

thanks leebenjp!

here is the pics


Last edited by AcousticBruce; 07/17/2009 at 01:46 AM.
AcousticBruce is offline   Reply With Quote
Old 07/16/2009, 10:19 PM   #2 (permalink)
Member
 
Join Date: Jul 2009
Posts: 1
Likes Received: 0
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I ran into the same problem. Using a Knoppix CD to boot and some google searches suggested it might be an overwritten .dll problem. I copied the msvcrt.dll from another installation to the broken one and I was able to get back into Windows. The "broken" one was last modified in 2000 compared to 2004 for the one that worked and was 1/3 smaller.
leebenjp is offline   Reply With Quote
Old 07/17/2009, 12:17 AM   #3 (permalink)
Member
 
Join Date: Jun 2009
Posts: 40
Likes Received: 0
Thanks: 9
Thanked 2 Times in 2 Posts
Default

Quote:
Originally Posted by leebenjp View Post
I ran into the same problem. Using a Knoppix CD to boot and some google searches suggested it might be an overwritten .dll problem. I copied the msvcrt.dll from another installation to the broken one and I was able to get back into Windows. The "broken" one was last modified in 2000 compared to 2004 for the one that worked and was 1/3 smaller.
Interesting. I have never heard of knoppix... but am reading about it right now. Looks like I will give it a shot... seems like a good cd to have around.

msvcrt.dll where do I get the dll file?
AcousticBruce is offline   Reply With Quote
Old 07/17/2009, 02:06 AM   #4 (permalink)
Member
 
Join Date: Jun 2009
Posts: 40
Likes Received: 0
Thanks: 9
Thanked 2 Times in 2 Posts
Default

Hey Leebenjp,

I got to ask.. how would one have found out the the msvcrt.dll is broken??
AcousticBruce is offline   Reply With Quote
Reply

 

Tags
blue screen, sdk

Thread Tools
Display Modes



 


Content Relevant URLs by vBSEO 3.6.0