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. 


DaGbyte

Member
  • Content Count

    37
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

0 Neutral

About DaGbyte

  1. OK, I rewrote the batch file (attached). I think I have it right. Anyone wanna check my math? Dunno if it is relevant, but I code alot in Winbatch. 2 of the scripts I have don't work. I'm using 2007e (I think it's E) and none of them work in PE 2.0. Is there some kind of EXE blocker in place? Maybe UAC of some kind??? I know in 1.x you had to initialize the WSH & HTA interface - that still the case? Any help is mucho appreciado!!! Mahalo, -DaG Build.cmd
  2. I created my ISO and made sure to add the packages before I unmounted and burned the image. However, when I try to make WMI or even HTA calls, I get nothing - no errors, no output - nothing. In 1.x you had to registre the apps and there was a whole bunch of regsvr32 commands that had to run. Is that still the case? How can I initialize the apps? Mahalo, -DaG
  3. I've seen that problem with the Fujitsu 5112 tablet. The fix I found, at least mith my version of PE, was to turn off the AHCI interface in the BIOS. Once I did that, I was golden. Trying to update my version of PE now to support SATA controllers, so if you have any input, please share
  4. Chris, you seem to have some experience with this, can you help? I have a PE build for a bootable USB drive. It was built using server 2003 and PE 2005. I run the following command to create the base build: MKIMG.CMD D:\WINPE2005\W2K3CD D:\WINPE2005\Builds\HDD /WMI /PNP /NOWF I copy a bunch of junk to the D:\WINPE2005\Builds\HDD folder (NIC drivers and other tools and stuff), but modified the WINPEOEM.SIF to look like this: [Version] signature="$Windows NT$" [OEMDriverParams] OemDriverRoot= "DRIVERS\Additional_OEM" OemDriverDirs= Dell5iR, IASTOR I copied the drivers to Minint\system32\DRIVERS\Additional_OEM\Dell5iR and Minint\system32\DRIVERS\Additional_OEM\IASTOR respectively. When I boot and hit F6 to load drivers, it says it sees the Intel 82801GBM SATA AHCI driver, but not the Dell SAS driver. If i copy the contents of the Dell5iR folder to a floppy and manually load the drivers, it loads just fine and I see my hard disks under PE. If I don't I only see my USB drive. I'm a pretty intelligent guy and don't think I've lost it yet - what could the problem be? I missing something, and hope it just me having a junior senior moment... Any help is appreciated... Mahalo, -DaG
  5. I've read a lot stuff out there. Not much was helpful for my specific quandary. I have an XP SP2 sysprep'ed image - that I cannot modify - that does not have the IASTOR drivers I need on it. I guess I should first ask the question; Can you add SATA drivers to a sysprep'ed image? I tried modifying the sysprep.inf file and that didn't work. I'm missing something, and I have no idea what. Anyone have any relative light than can shed on the issue? I can't imagine I'm the first guy on the planet having this issue... Mahalo, -DaG
  6. I used CreateUser to add accounts en masse. I would concatenate cells in Excel and make batch files that added the users to the specified OU's. Is there a machine account version of CreateUser out there? One where I can pass OU and Computer names and a description? I could probably make one, but my laziness has gotten the best of me and I'm a little too busy to. ANy help is appreicated! Mahalo, -DaG
  7. Not quite sure what you mean about the debug stuff - I'm not very up on that. It was built with a corp XP copy w/SP slipstreamed into it. I'll try to reapply SP2 and see if that helps....
  8. Listed below is the bugcheck. My guess is something got corrupted. Just what and how to fix it remains a mystery... Microsoft ® Windows Debugger Version 6.5.0003.7 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [C:\Temp\Mini102805-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0 Debug session time: Fri Oct 28 08:02:40.921 2005 (GMT-5) System Uptime: 2 days 0:56:05.632 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols .................................................................................................... .................... Loading unloaded module list ................ Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007E, {c0000005, 0, b2426188, b2425e84} ***** Kernel symbols are WRONG. Please fix symbols to do analysis. Unable to load image rdpdr.sys, Win32 error 2 *** WARNING: Unable to verify timestamp for rdpdr.sys *** ERROR: Module load completed but symbols could not be loaded for rdpdr.sys ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* *** WARNING: Unable to verify timestamp for termdd.sys *** ERROR: Module load completed but symbols could not be loaded for termdd.sys *** WARNING: Unable to verify timestamp for RDPWD.SYS *** ERROR: Module load completed but symbols could not be loaded for RDPWD.SYS *** WARNING: Unable to verify timestamp for TDTCP.SYS *** ERROR: Module load completed but symbols could not be loaded for TDTCP.SYS Probably caused by : rdpdr.sys ( rdpdr+25f49 ) Followup: MachineOwner ---------
  9. I have an easily reproducable issue. I am running XP SP2 on my laptop and whenever I remote into via RDP (termial services) and try to copy a file to the clipboard, to copy to my local machine, the laptop bluescreens and reboots. I viewed the bugcheck and the only thing that jumps out at me indicates there is an issue with the remote deskop application. I've run all critical updates but cannot fix the issue. RDP works just fine otherwise, just when I copy anything to the clipboard remotely, it reboots. Has anyone seen anything like this? Any ideas how to fix the problem? It's not a component I can remove and re-install, so I'm kinda stumped.... -DaG
  10. RDP - MS Terminal Service - remote control. Whenever I connect to my laptop and choose to client drives and try to copy data from my laptop to the clipboard, presumably to copy it to my local machine, my laptop blusescreens. My laptop is the host. I've applied all the service packs, and everyhting seems to be working the way it's supposed to, but every single time I try to cut and paste, boom. I do not see where I can remove the component in add/remove. ANy suggestions?? Anyone else ever see this??
  11. I have an easily reproducable problem. When I RDP into my XP SP2 mcahine and attempt to copy files to the clipboard, it luescreens. Every time. I looked at the .dmp file and the only drive I could find was RDPDR.SYS. Any ideas??
  12. Nope - No RIS. I have been building my PE images for some time w/XP SP2 and it's been wokring great. I can even boot from the OEM CD into PE. But for some reason, something's not getting loaded...
  13. I read on a thread somewhere that 2005 may support a NIC I'm trying to load (Intel pro/1000 on an IBM M52). So I grabbed my trust PE 2005 CD and did the following: --> Made a dir called D:\WINPE2005 --> Copied the WINPE folder from CD to D:\WINPE2005 --> Made a dir called D:\WINPE2005\W2K3CD --> Copied my 2003 Server w/SP1 into that folder --> Ran MKIMG and created a build for HDD's --> Copied the build to a USB HDD Now, I've been using this procedure for my older version of PE and it's been working just fine. However, this seems to not be working. When the white line changes from "Launchine Windows PE..." to Please Wait, it just sits there. ALmost like I missing something. Any ideas?? -DaG
  14. As far as I know, if you inject the .DRV & .INF file for your NIC into the INF and DRIVER folders on the iSO, you should be good to go. You can load XP and look in device manager to see what files you need. Let me know how you make out...
  15. The way I do my builds now is I launch MKIMG.CMD and in that batch file, I copy my drivers in my \Drivers folder to my build folder: xcopy .\Drivers\*.* %WINPEDESTDIR%\%PLATEXT% /e /v /i /y In the Drivers folder I have my INF folder and my system32\Drivers folder where the corresponding file exist. I was under the impression that PE reads the INF files at boot up abd loads the corresponding driver for it. What I want to do is be able to inject NEW files (.INF and .SYS) into a ghost image so I don't have to snap a new copy of it. Am I crazy or is that not how it works?? -DaG
×
×
  • Create New...