Jump to content

FastRedPonyCar

Member
  • Posts

    28
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by FastRedPonyCar

  1. I've been trying to wrap my head around imagex and it seems so simple in concept but for some reason, I'm having the hardest time understanding how to capture an image with it. there's some concept it seems with the capturing process that the windows AIK help file documenting how to use imagex and all of the online how to's I've read seem like they're almost assuming that I know how to do something important that I'm not. I'm missing out on some concept that I feel is just absent from these tutorials. Here's where I'm at. I've got a laptop I've installed and customized vista on and sysprepped. I've used AIK to build a winPE disk with imagex and a generic config file for file exclusions and I can boot that disk into winpe, browse the disk and see image x. I'm trying to run the command they give to capture the image but it doesn't seem to be working. Now... here's where I'm confused. They say to run the command prompt for imagex on the technician computer (which is my main computer with windows AIK installed on it) but how am I supposed to capture an image of the laptop sitting next to me on the desk if I'm opening up imagex on my main "technician" computer??? also worth mentioning is that I've got the laptop hooked into a switch that an image server is attached to. I've tried running Net use m: \\servername\images$ (where the images are stored on C:\images$ on the server's hdd) and I get the error "the network name cannot be found" It's part of a workgroup called "pcconfig" so I tried Net use m: \\pcconfig\servername\images$ and it says "the network path cannot be found" Is there some big picture concept that I'm missing here?? Please help! Oh, Also worth nothing is that I can boot up norton ghost and capture or load images from that same images$ share so I know there's nothing wrong with the hardware.
  2. I hear it's not when you're a MSDN member/tester... which I am.
  3. I'm rocking 6895 here also. I've tested a few various Vlite builds of it on 3 different systems. My main one is my HP 8510p notebook, another is a Dell D630 notebook and the 3rd one is an ancient Gateway E series that has 1 gig of ram and a 2.4 ghz PIII cpu. I'm shocked at how fast this OS runs. I thought folks were just blowing smoke when they claimed it was as fast, if not faster than XP. Man they were right. On that Gateway, straight out of a fresh install, it's a hair quicker than a fresh XP install with all patches and SP3. A few drivers that aren't supported (intel video drivers) but it does a nice job of stopping the loading process and asking you to go to last known good config. The interface runs smoothly on all systems as wel. Much quicker using Aero than with Vista and system resources are more or less almost all there. I'm also getting that error with the unattended setup though. It's not a huge deal though. I'm going to try to run a sysprep proceedure like with vista that has all of the info filled out to see if it works or not.
  4. I'm not sure about the registry stuff but KB838804 is supposed to be one patch for this. http://support.microsoft.com/kb/838804
  5. yeah that would be it. Apparently my name and phone number made it's way up into the upper eschelons of Mcafee's support team and they're going to be calling me sometime soon. One tidbit I was able to gather though was that there's something to do with the kernel running out of space and increasing the kernel size or adding a kernel size key to the registry MAY fix the issue.
  6. We've recently deployed HBSS and our Server 2K boxes are bluescreening. I got an email saying that there are issues between win2K servers and HBSS when using remote desktop and HIPS (Host Intrusion Prevention System), There was mention of a hotfix released that addresses this problem but I'm having trouble finding out which hotfix it is. any of you guys know which one we need?
  7. Let me bump this old topic up as it's something I'm trying to figure out here at work. Windows updates is disabled via registry/group policy settings. Our lab managers can't change them and are required to update machines with microsoft MBSA 2.1. The scan runs fine and returns the results saying what patches you need. Rather than downloading exe updates, it only will download cab files for the MS08-XX update. Is there any way to get MBSA to download the actual EXE file rather than a cab file or is there something I'm supposed to do in vista to install these updates using the cab files it gets? I swear 2.1 is the dumbest thing ever. 2.0 worked great, grabbed EXE files and just did what it needed to but it's incompatibility with Vista sucks.
  8. Sorry I forgot to mention that! The images we get have the group policy and registry locked down so that the windows updates are disabled (as we use SMS to keep the machines up to date) The problem is that we USED to be able to use our own images that were kept up to date and now we can't so we're trying to find a faster way to get a machine up to date before putting them on the network. Anyways, I found this. Works BRILLIANTLY (and faster than windows update) http://www.autopatcher.com/
  9. Ok I've got builds of both 32 an 64 bit vista and I'm looking for something that can be run after an install (which includes SP1) that can automatically go and grab any updates and install them without countless pesky UAC prompts. Does such a tool exist? I've installed MBSA 2.1 on one of each and it shows what the machine needs patched but the download link goes and grabs a cab file that I have no idea what do to with. I've gone out and manually downloaded the actual MS08 exe files but with around 25 of them needed after a clean install, it's tedious and time consuming and I need something that can do all of this automatically. Any ideas or programs that can help speed this up?
  10. OK some guy brought a dell precision 360 desktop into our shop and it has a SCSI hdd adaptor and 2 western digital IDE drives, each in an SCSI cradle that plugs into the SCSI to IDE adaptor. I was fairly sure I'd need to do the whole F6 to load SCSI drivers before XP install begins but before the machine even POSTS, it comes up saying no primary HDD found. Bios says "unknown device" as primary IDE drive. The actual harddrive is perfectly fine as I took the drive out of it's little SCSI adaptor module and just plugged it straight up to the mobo with an IDE cable. It's loading XP right now. The problem is, there's a 2nd hdd in it's scsi tray that he wants XP on as well so that he can do the whole hot swap thing with the drives. I don't have another SCSI to IDE adaptor around to try and see if the actual adaptor that these hdd modules are sliding into is bad or if there's just something I'm not doing to allow the PC to SEE that adaptor. Can anyone shed some light on what could be wrong here? BTW, I hit up dell's site and downloaded the scsi drivers, put them on a floppy , loaded them with F6 before the xp install but it comes back saying no hdd found to install the OS to.
  11. FIXED!! I deleted C:\WINDOWS\system32\drivers\WimFltr.sys Then re-started Vlite and told it to install, then I selected ultimate again and now it's good (hopefully to stay)
  12. I've got the X86 wim filter in the X86 program files Vlite folder, I've right clicked on the X86 file to install the driver. Vlite fires up fine, sees my files on the desktop that I copied from the dvd and then when I click ultimate, I get the mounting image error -code: -2147024894 It asks to restart which I've done twice. What am I doing wrong? search function yielded nothing Edit: I'm running vista 64 to do all this.
  13. because if you do SP1 then hotfixes, you'll get the ntoskrnl.exe corrupted error message when it loads the setup files. for some reason, it works when you integrate the post sp1 hotfixes first. I slipstream SP1 and then integrate the hotfixes and I have never received any error when installing. have you removed any components and still had it install without errors?
  14. because if you do SP1 then hotfixes, you'll get the ntoskrnl.exe corrupted error message when it loads the setup files. for some reason, it works when you integrate the post sp1 hotfixes first.
  15. for you guys having trouble, try taking just the oem out of the box iso, slipstream SP1 and apply that then create the iso, burn it to disk. Don't touch anything else, not even the automated install. Just SP1 and that's it, no other hotfixes. install vista and then run a windows update and write down all the patches that it finds that you need. What I did was use a vista updates downloader that scanned my PC and downloaded the individual kb packages. Next: Take the original disk and open Vlite back up and use the original disk's data as the foundation, NOT the one you have slipstreamed SP1 with. Now once Vlite is open, skip the service pack option and ONLY integrate the patches that the OS said you needed after you just ran the windows update, I also ticked the 4 gig ram fix also. Now, DONT remove anything. Apply, rebuild and burn that to disk. Now, take THAT disk's data and use it as the foundation for your next build. At this point, slipstream SP1 but again, do NOT remove any components. Apply and build the iso. Now, for the final build, you should have a disk that has the post SP1 hotfixes integrated as well as SP1 slipstreamed and NOTHING else removed. Take this disk and use Vlite to use it's contents to start removing components, automated install, etc... If you do it like this, it SHOULD work and best of all, windows updates should work without giving the reboot loop. I've built 4 install disks from scratch this way and can verify that for me, it's worked flawlessly every time. For whatever reason, if you integrate the post SP1 hotfixes, rebuilt, slipstream SP1, rebuild then strip down, rebuild, it works with no errors trying to install patches or anything like that.
  16. Removing cpl and uac are fine. I've yanked both of them out and the os is functioning fine (so far as I can tell)
  17. Not unless you want to stare at the "NTOSKRNL.exe is corrupted" error message rather than a shiny colorful "installing vista" screen Thared33 is to credit for showing me this. http://www.msfn.org/board/Important-Proble...lu-t118152.html
  18. I've gotten near total success at this point with my current build of ultimate 32X. First I integrated all 30 something odd hotfixes that show up after a SP1 os install. So at this point, it's just an out of the box, non SP1 build with all the post SP1 hotfixes integrated, built the iso and verified that it installed with no issues. Then I fired up Vlite again and this time, used that build as the foundation for the next iteration which all I did was slipstream SP1. I installed the OS once again to verify that it had SP1 and the hotfixes. Microsoft updates showed no avilable updates at that time so everything was patched and up to date. Final step was to strip unwanted stuff from the build and then make the final iso. Here's where the problem is. Now, the actual build process is fine and it installs fine with no issues but apparently none of the unattended setup information is retained. I don't know if this has been addressed yet but for whatever reason, despite putting in the product key, time zone info, user name, etc...and applying the changes, it still takes me to these screens during setup and when I get into the OS, going to my computer properties shows that it didn't take the cd key during the Vlite build. Every other change is retained. aside from that minor inconvenience, everything works great.
  19. I've got a question. You say to check the UAC control to remove it but I get a message saying that "run legacy CPL" needs that to function and for the legacy CPL item, you say to leave it. So what's the deal?
  20. I use acid pro 6 and I've used reaper on and off as well. With 2 gigs of ddr2 1066 ram and an E6600 intel CPU, it was a pig but once I upgraded my core system to an E8400 clocked up to 3.8ghz and 4 gigs of corsair XMS ddr2 800, the latency practically vanished. But like you, I do slather on the plugins and I'll have up to 8 or 9 guitar tracks all with various eq plugins, compressor, reverbs, delays, etc.. each track is different and having to play all these tracks and process all the plugin chains simultaneously... yeah I can see how you'd need as much raw processing power as possible.
  21. Maybe a little bit offtopic, but you use Windows Vista in a recording/studio environment. Do you have the same performance as with Windows XP? I ask this because I have a studio Pc myself and tried it with Vista and it gave me around 20% performance loss while using Vista in comparison with Windows XP. I do home pc recording as well and 2 of my sound cards had bad latency issues with vista but not with XP. I'm not hardcore into the recording like most studio guys are but I do my fair share and the drum software I use (EZ drummer) sucks down RAM like candy.
  22. thanks for the tip as I've stumbled upon the NTOSKRNL error as well. Like you, I did a build with SP1 slipstream then made another one integrating the 4 gig ram fix and about 30 patches that show up after the SP1 vista install as hotfixes that have been released since SP1. now, I'm looking at Vlite telling me that KB937286 (patch to upgrade online help feature) and KB940157 (search 4.0 application - don't need it anyways) integration failed. They both installed fine from within the OS using MS updates. I'm by no means concerned that these 2 couldn't be integrated but it begs me to wonder if others in the future won't be able to be integrated and why this is?
  23. yup. all the updates installed fine, no loop. I've rebuilt the iso with all the updates and SP1 and haven't modified the components yet. Will be installing shortly.
  24. SP1 integration went well and installed fine. Running all the windows updates as we speak. Question (and I'm sure the answer is no) but does the fact that I haven't activated windows yet have any impact on the success of the install of the patches and updates? Regardless, I'm going to write down which updates fail then try and manually run the install package. If some still don't work, I'll return with a list of the failed patches to see if anyone else has the problem with them. It'll be interesting to see which of them get successfully integrated in Vlite when I rebuild it again today. Basically I'm trying to do this one step at a time. I know the oem disk works; I now know that the SP1 slipstream disk works. If the updates all work fine without tossing me into the reboot loop, I'll proceed with another vlite build with all the available patches and updates, verify the success of the install and then finally see whether or not it will let me start yanking components out at that point and still sucessfully install.


×
×
  • Create New...