Jump to content

Thared33

Member
  • Posts

    12
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About Thared33

Thared33's Achievements

0

Reputation

  1. One last note. The thing is -- with this, is that I don't know if this will only apply to the KB929777 hotfix, or every hotfix out there that was released before SP1. SP1 is fairly recent/new, so this might be a problem for some. I believe the KB929777 hotfix was released in late 2006 or so, and SP1 was just a few weeks ago or so. Maybe it's in general and not just the 929777 4GB hotfix -- applying it after integrating SP1 is the problem; then again, maybe it's just that hotfix. I seriously don't want to keep testing it and waste even more DVDRs Another note is that I'm using the 64bit version of Home Premium, and I had to use the x64 version of SP1. I'm not sure if others will have the same problem with the x86 version at all, or other specs in general. This applies to my setup only, but I'm thinking it will be more of a general thing. I hope this clears some stuff up.
  2. It's amazing -- how common all of these errors are. What my system did was just hangup and there was no reviving it. It just completely froze -- everything. It's like you're looking at a picture file/a screenshot of a desktop. The mouse won't move, and audio won't work. I increased my ram from the default setting (I'm thinking it was at 1.9V...) to somewhere around 2.2V. I had to look on forums for hours and hours and saw that increasing your ram voltage will cure it. It would hang up on me in under one hour of being in Vista, and after I upped the voltage, no more hang ups. I can run Vista for as long as I want and it's perfect now. I actually saw a tech that works for Corsair post on the Corsair forum; he said to up the ram voltage to another user with the same hangup problem, so that's what made me ultimately want to try it (since it came directly from a Corsair tech). I was a bit scared of doing that at first, but things are working just fine now. Motherboards seem to have a problem with powering up fully-populated ram slots.
  3. http://www.msfn.org/board/Important-Proble...lu-t118152.html I solved it. Maybe this will help others as well.
  4. One more misc. thought. It is beyond me as to why MS would release an OS when KNOWING that installing Vista on a system with 4GB of ram or more would give all of us errors. Many people don't know how to get around this or aren't capable of being that computer savvy, so I'm sure all hell has been breaking loose over stuff like this Thank god for Vlite though . I almost seriously gave up on Vista and wanted to revert back to XP, with a 4GB ram limitation =/. I need 8GB of ram because this is a recording/studio PC.
  5. I posted a thread about it, and someone else did as well; it seems a few others are having trouble with this, so here is the entire ordeal with solutions included. Concerning Vlite: Vista would not boot with more than 4GB of ram, so I decided to integrate SP1 with Vlite to avoid having to take ram out of my system every single time I needed to format. I discovered that it isn't SP1 that fixes this, but the hotfix located at http://support.microsoft.com/kb/929777 . I integrated SP1 and tried it, and it still gave me the BSOD when trying to install/boot. After this, I tried integrating SP1 and THEN the hotfix, but it kept giving me an error saying that ntoskrnl.exe could not be found. Booting with only SP1 integrated would get me to the 'loading' screen of Vista, but only along with the BSOD because the hotfix wasn't added. After integrating SP1 and then applying the kb929777 hotfix, it gave me the 'ntoskrnl.exe could not be found' error/screen. It is noted that you should only apply hotfixes with vlite AFTER you integrate SP1, but let me explain why this isn't always true. Integrating SP1 only would get me further along in the install process than with the hotfix because it would go to the Vista screen with the green bar that scrolls, but it'd give me the BSOD because the 4GB hotfix wasn't applied. When I tried integrating SP1 and THEN applying the hotfix (as it says -- you should apply hotfixes only after integrating SP1), it would give me a new error saying that ntoskrnl.exe wasn't found. I wasted a grand total of 8 or so DVDRs with tying to get this working, but the 9th one worked (and I have to mention that my 9th DVDR happened to be my very last blank DVDR ). Let's see how I did it. After integrating SP1 and having the BSOD, I tried integrating, and then the hotfix; however, along with the hotfix -- I decided to use an unattended setup, as well as tweaks. I started thinking that maybe the tweaks/unattended setup was messing it up, so I did nothing but integrate SP1, then apply the hotfix, but still got the same error =/ I tried all kinds of methods as far as what to take out/apply to Vlite, and also integrating, closing the program, then coming back, etc -- all kinds of combinations, but none worked and it gave me the same error. I decided to apply the Hotfix ONLY and not SP1, and to my surprise, it started working with 8GB of ram installed. Both SP1 alone was working (but BSOD because of no hotfix), and the hotfix alone was working. I avoided applying any hotfixes whatsoever because it says in the program (also in guides) that applying hotfixes must be done AFTER SP1 is integrated, but this time it isn't so true. What I did on my last try/last DVDR was apply the 4GB hotfix to a fresh copy of Vista, and then integrate SP1, even though I had to go against what I had been hearing. I also decided to do the tweaks and an unattended setup, although I thought that might have been what was giving me the errors. Apply the KB929777 hotfix BEFORE you integrate SP1, and make sure that when you insert it into Vlite -- click the '4GB fix' option that puts a check mark into the program so it will work when you're trying to install it as well. After this is applied, integrate SP1 and all other hotfixes, as well as any other modifications and the unattended setup. The reason I'm making this long/a big deal out of this is because the possibilities for errors may be endless because this is only what I was experiencing -- not including the other trouble others may have. Some thoughts that come to mind is that maybe it's necessary to apply hotfixes before SP1 was out BEFORE you integrate SP1, and then hotfixes released after SP1 are ok to put on after SP1 is integrated. I think this is where my trouble came from. I think this will be an important thread because these days -- most will want 4GB ram when installing Vista, and I think Vlite users will try to do the same method that I'm doing. Maybe some of this info should be added into the program help/the guide on the site? Other problems not related to Vlite, but very important. Vista doesn't like 4GB of ram when installing/booting, so the hotfix mentioned above is necessary. Taking out your ram is a pain -- especially if you format a lot, so Vlite seems like a logical option. However, there is another problem here: hang ups. I started getting random system hang ups and I had no idea why. I discovered that increasing your ram voltage solves the problem. It seems that motherboards/Vista/etc have a hard time powering up a full 8GB of ram (because it's all 4 slots), so increasing your ram voltage is necessary with Vista if you're getting random system hangups. Ohhh god does Vista not like ram... After a couple of weeks and countless hours of testing/tweaking/crying in between, I finally have a fully-working system with no problems. Here's how I did it. Increase your ram voltage if you have system hang ups. Mine was set at about 1.9v, so I increased it to somewhere around 2.2V, after much research. No more hang ups! Copy your Vista files to your HD Apply kb929777 hotfix in vlite (make sure to 'tick' the 4GB box that appears in Vlite after inserting it) Integrate SP1 (make sure you apply hotfix kb929777 BEFORE integrating SP1) Apply any other settings in vlite Burn directly, make iso, etc That should take care of it. It took me a couple of weeks and many hours of testing/researching to figure all of this out, but it's finally done. The system hangups because of the ram voltage made me almost give up, and then getting Vlite to make a proper working version didn't help, but I got over all of it just fine. I thought I'd leave my experiences here for everyone to see because I think it'd be useful. I'll stick around for a bit longer, but I won't be visiting the forum in the future very much since I worked out my problems =) My system specs are below. Intel Q6700 Quadcore 8GB Corsair Ram Asus P5N-E SLI 2 500GB SATA HDs Nvidia Geforce 8600GT Windows Vista Home Premium (64bit) Let me know if anyone has any questions.
  6. Hmm.Does the error occur when you enter DVD and it says Loading Files? The error occurs right after it says 'windows is loading/copying file' in the command prompt-looking window. The bar goes full, and then the screen comes on and says that ntoskernal is missing. Won't go any further than that, and I think it's probably the same for him.
  7. Weird. I didn't see this thread and posted one right after you did. I have the same exact error and I don't know why. I decided to not remove any components.. Just added a hotfix, SP1 and did a simple unattended setup. I'm not sure what's going on. I tried simply adding SP1 and it got further along in the install than when I add a hotfix/use the unattended setup. See my thread right next to this one.
  8. I just checked the folder. There is a file called ntoskrnl-dl.man in the /sources/dlmanifests directory. That's all there is as far as a file called ntoskrnl. I'm not sure how I'd get to the /system32 folder... Which file should I mount in gimagex?
  9. Where would it be located at in the vista install files? Gimage opens images files, so I'm not sure which file that that would be in.
  10. I've made a couple different Vlite installs of Vista (x64 Home Premium), but this error comes up each time -- on both of them. I'm thinking that everything would be ok if I could get around this, but I'm not sure what's causing it. It says that the file ntoskrnl.exe is either corrupt or missing and won't boot.. and says it right after the 'windows is loading files' page when booting with the DVDR in your drive. I didn't do very much to my installs -- just a few things. I added SP1, the only hotfix I applied was the 4GBfix, and I tweaked it a bit with the unattended setup and disabled UAC, etc. Just simple stuff. I made sure to integrate SP1, and THEN do the rest of it (although I didn't hit Apply until after all of my settings were done). I'm not sure what's going on here.
×
×
  • Create New...