bluescreens
Content Type
Profiles
Forums
Events
Posts posted by bluescreens
-
-
No, I checked it in both the normal mode and the safe mode. The driver Z is not one of the hard disk partition.
I found the drive letter Z in the
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2
where all the other drive letters are there.
I tried to delete the Z letter, but it is restored when I close the regedit and re-run it again.
No idea why can't I delete it
I'm unable to parse your answer. Does this happen in safe mode?
Does this happen in normal mode when you log in as another administrative user that you've created?
0 -
(BartPE is the only image I run and all .OSC screens are automated so BartPE starts right up after pressing F12);
Interesting. Can you share how you did that step? I'm familiar with renaming the startrom.n12 bit; what else did you do?
0 -
Thanks for the reply.
It is not in the diskmgmt tool. I have four partitions, C, D, E, F, CD-Rom is using G. No letter Z at all.
I don't know where it comes from
Please help
Ray
Do you see it in safe mode?
0 -
1. I have just installed many hotfixes to my fresh WXP Pro SP2 EN. But I have big problem to do so with last 25 fixes. I run KBxxxxxx but installation process never ends. It stops at 'inspecting system' or at 'making restore point' as I can see on my screen. Sometimes installing one hotfix is successful but next one not.
In taskmanager I can see KBxxxxxx proces that has 0% CPU time, update process with 0% CPU time and one of svchosts has 100% CPU time. It can last for hours without any result. Restarting PC does not help.
2. My second problem is with hotfixes integration. When I try to integrate more than 200 hotfixes, installation process never goes over t39.
Is there any way to fix these "bugs", at least the first one. I don't want reinstal the whole system.
Pleas, help me.
Thank you.
Microsoft *agressively* supports all hotfixes. If you have a problem with installing them, call the normal PSS supportline, and they'll help you install the hotfixes on your system (for free). If you want help with slipstreaming it, there would be a charge for that, but one-off installs are absolutely free.
The c:\windows\KBxxxx.log file doesn't tell you anything?
Same thing happens in safe mode?
0 -
Hi Nois3,
Can you please point me to the thread where you argue why not to use Ghost. I was unable to find it. I'm curious why you would so strongly discourage the use of Ghost when even Microsoft itself seems to advocate its use. What pitfalls am I getting into that I might not be aware of?
The ones I am so far are;
HAL issues
Drivers issues (Esp. for Mass Storage)
Hardware SID
Cheers.
Don't use Ghost alone. Use it in conjunction with Sysprep (available by searching for "deployment tools" at Microsoft, and typically in the DOCS directory on the XPSP2 and 2003 CDs you get from vendors). 2003's sysprep works great with XP.
When used correctly with Sysprep and a little bit of knowledge, Ghost is a good tool that cleanly handles driver issues (mass storage included), SIDs, and ... just about everything except HAL issues.
0 -
Use Ghost and I'll guarentee you you will have problems later. I'm speaking from 15 years of experience of corporate support. I am just saying this as a lesson learned: DO NOT USE GHOST TO DEPLOY WINDOWS
I also do not wish to argue this point with the Ghost supporters. I consider them amatures, and they usually just keep making excuses and work-arounds for Ghosts (or any image deployment) shortcommings. They just like to use Ghost because it's easy and they don't have to understand how real deployments work. They don't usually support a large infrastructure. Few of them understand how link-tracking, SSIDS, Registry permissions and default profiles work - all of which are affected by image based deployment.
The problems encountered by users of Ghost deployed images are usually not recognized by the support staff. They chalk up the intermittent application crashes and slow response times to "Windows Bugs" or some such thing.
Again, I do not wish to argue this point again in these forums, you can do a search where I argued this point last year in detail. I just bring this up again because I hate to see image deployed buggy installations give XP a bad reputation because some amature admin doesn't know what the hell he's doing.
Ghost itself is only designed to copy the core image. You need to do some prep work before the core image is ready - including Sysprep and including some other (documented) steps. If you don't do this, or don't completely understand how to do this, yes, there are problems.
If you do do this, though, Sysprep+Ghost works great. You can easily deploy to all PCs no matter what drivers and hardware they have, and Sysprep will intelligently go thru your drivers and pick the right ones, every time. Builds are fast and, with a fast local network, very trouble-free.
That said, with a $3-5 per PC licensing fee and with a monolithic setup (want to update a single driver file for a single PC in your ghost image? You'll need to distribute the full Ghost file to all your sites again, not just the 200-300KB in updates, plus you'll need to rebuild the Ghost file) it's not suited for what I'd call enterprise deployment and a constantly changing enterprise environment. For the OP, though, in all honesty it would probably be good enough.
That's why I like RIS. It's a breeze to update, whether you have 10 servers or 100, and you can push 100KB changefiles out easily. It's very well supported by Microsoft, and you don't need to worry about HAL issues (if Microsoft finds out you forced the HAL on your PCs, they won't support your problems.)
0 -
Ok, lets say your in a senario where you need to have a deployable corporate SOE (Standard Operating Environment), and you only have 5weeks.
The SOE has to be deployable on 11-14lines of different hardware.
You have no available application deployment infrustructure (RE: SMS etc..).
The SOE needs the usual: WinXP+Patches, MS Office+Patches, PDF Reader, AV Software, Java, Citrix Client, Flash, Quicktime.. etc..
The SOE will then need to be deployed on 55 (in use) machines in a proceeding 4week period... more later.
Please rule out external help, design, etc.. at this stage.
How would you approach this senario? (Helpful comments only please)
1. On your 2003 servers (you DO have 2003 servers, right?) add the RIS service.
2. Add an XPSP2 image to the RIS server, using an update.bat or similar textfile as the kickoff batch file to run once XP is installed.
3. In update.bat, install all the hotfixes you want, install all the applications you want, and do all the other things you want.
All done.
If you have some idea of the drivers you need, you can include them too. For example, in the [unattend] section of ristndrd.sif, put in something like:
[unattended]
DriverSigningPolicy = Ignore
OemPreinstall = yes
OemPnPDriversPath="x\c\intel;x\card\o2micro;x\card\ti;x\m\conexant;x\m\pctel;x\n\3c90x;x\n\broadcom"
...and put in the appropriate .sys/.inf drivers for that hardware (above, intel chipsets, o2micro cardbus drivers, ti cardbus drivers, conexant modem drivers, pctel modem drivers, 3c90x nic drivers, broadcom nic drivers.)
0 -
Small problem. RIS server is win2k3. I'm trying to get a new XP profile to install and join to a domain automatically. I've searched the forums and on google. I've tried several suggestions, but none have worked. Here is the error I receive.
Network Configuration
The user you have specified is not permitted to join the machine to the domain. Would you like to proceed for now and try joining the domain later?
If I choose no and enter the same username and password I always use then it joins the domain and all is good until it tries to AutoLogon for the first time. At that point I get another error.
Logon Message
Your account has been disabled. Please see your system administrator
The reason it is saying that is because in the "Log on to:" field the computer name is there instead of the domain and the username account I'm trying to login with is not on the local pc, but on the domain. If I select the domain and login with the user name and password I always use, it works fine.
Anyone know what I'm doing wrong?
Here is my .sif file
____
What, exactly, is "the same name and password you always use"? Is that the same name and password as what you use in the blue screens to log into the RIS server and see the RIS images? If not, that's your problem. If so, then that user account (the RIS name/pw you're using to build the PC, at the blue screen) has probably joined 10+ PCs to the domain, which is the limit, and you'll need to fix that seperately (if that's the issue LMK and I'll help you search Microsoft.com for the solution).
The second issue is normal - you're prompted to log into the local machine rather than the domain; change the third prompt to your domain, and you'll be able to log in normally.
To me it looks like you're all OK, aside from the name/password bit...
0 -
It won't; that's what it's there for - learn how to clean it too; it's all in the MS KB articles.
Well, [sysprepcleanup] is automatically generated by the BuildMassStorageSection=Yes. And if you are talking about sysprep -clean in your commandlines.txt in the \Sysprep\$OEM$, I knew of that already.
I guess the reason for my asking is I have heard some skepticism over the line in sysprep and I really need other people’s opinions. If in the end it is going to end up hurting me, which it doesn't look like the case, I'll take it out, but if this isn't the case I would like to know that as well.
I'm just in search of the truth.
Sysprep is supported by the people that wrote the operating system. That's a pretty strong show of support. That command is specifically put in there to address XP's inability to cleanly PnP disk controllers that it doesn't know about beforehand.
Did you have a specific question?
0 -
Hello all
I have just recently discovered the wonders of:
[Sysprep]
BuildMassStorageSection=YesAnd I was wondering if there were any CONS to using this. It seems to solve alot of issues with imaging on multiple hardware sets
: , but I didn't know if it would hurt me in the long run . Please anyone and every one answer as I need every ones experience with this.Thanks!
It won't; that's what it's there for - learn how to clean it too; it's all in the MS KB articles.
0 -
with any of the hardware. I even have a HDD in there that I formatted with my XP Pro PC just in case. My problem is that I put the first CD, boot the computer up and the "Please wait while setup determines your hardware configuration..." comes up and then nothing. A black screen comes up and it just sits there. I took the
When you see the "Press F6 to specify hardware disk drivers", hit F6 and put in your SATA driver floppy.
That should let you then proceed.
0 -
Yes we do have AD but users have no rights to install anything including printers and oh by the way we currently don't use a print server. Does anyone know of a script I can use???
http://support.microsoft.com/kb/314486/en-us
Bear in mind you'll be fine if you make this a *machine* based startup script; it runs in the System context, so no worries about user access.
0 -
We have 12 printers on our network and all have their own IP addresses. There are about 150 users using these printers in different locations at different times. All 12 printers have been installed on all the computers. We just purchased a new color printer and I need to give access to everyone. The only option I know now is to log in as either admin or myself and install the drivers and I have to do this on all 200+ computers we have. Is there a way that I can use a policy or network install to save me the headache of going from one office to another?
Any help will be greatly appreciated.
I suggest a GPO based, machine based script that maps printers as appropriate every time the machine starts up. Simple, easy to maintain....
A way to dress it up a bit is to script it so that only certain subnets get certain printers, but that may be more trouble than you want to mess with.
0 -
Almost using no firewalls
You'd be surprised which programs and games try to send outgoing and and whereto. I've had image editors try to send to Microsoft, and didn't realize until my software firewall told me! If you have a router that monitors incoming and outgoing, that's fine, but I've heard that it slows down your connection overall due to the excessive packet monitoring done through the router. Makes sense.
Sure, but the same thing is happening on your PC.
I just use the MS firewall - and focus on not running malware in the first place.
0 -
I'm still not entirely sure whether this belongs in the software- of hardware-section, but anyway...
My mother got her self a nice ASUS laptop 2 months ago and everything seems to be working fine. It also has all the pre-installed junk on it, *cough*Norton Internet Security*cough*. But I also noticed the harddisk is formated with a FAT32 table, and on the desktop they put a batch-file to convert everything to NTFS.
Now my question is; Is this conversion process risk free? I mean, will all the files be still intact?
Thanks in advance
Everything has risk; this is a low-risk affair.
I disagree with a previous poster's suggestion to stick with FAT32. FAT32 is obsolete, error-prone, not journaled, and has issues with large files, with unexpected shutdowns, with power outages, and every time you sneeze on it. FAT32 is obsolete; let it die, and move to the current NTFS.
0 -
Windows default.
No issues, no compatibility problems, no hassles, works with everything, etc., etc., etc. Plus it's free.
0 -
Hi,
Out of impatience I've tried RIS with the PROSet 10.3 drivers - as is (i.e. I've not waited for any further relaease of a RIS specific version).
EDIT: RIS specific drivers have now been released. They have been tested and work fine.
The result is that on any 10/100 or gigabit system I've tried, inc. the D945GTP platform, everything has worked.
I can thoroughly reccommend an upgrade to 10.3 if you are experiencing any issues with Intel NICs and RIS.
Cheers,
Andy
ps - Only big chnage I noticed was to the file set for 10 Gigabit cards. They've changed some names and added another sys file. I don't have the hardware available to test this on at the moment, but if anyone knows anything about whether these latest drivers work with this hardware under RIS I'd be glad to know.
Are you guys applying 2003 hotfix KB823658 (or 2003 SP1)? That should allow just about anyone's INFs to work....and is vastly easier than waiting for RIS-specific INFs or <shudder> modifying them. Cost to get it is $0 - just call up MS and tell 'em you want it.
0 -
Using 2003 RIS Server to deploy XP SP2 image (with all drivers installed)
Image deploys ok to machine but when the 'mini-setup', sysprep runs for the first time it takes upto 9 mins for windows to install the network components.
After this long pause, the machine successfully joins the domain.
The machine in question is a HP nc6220 laptop which as a Broadcom NIC, Intel Pro/Wireless 2200BG NIC and integrated Bluetooth.
___
Sorry - I don't understand.
If you're using the RIS server to deploy XPSP2 images, where does Sysprep come into this?
You're using RIS to deploy the image, then Sysprepping the result for some reason? Why?
0 -
see http://www.msfn.org/board/index.php?showtopic=48392&hl=yukon
search here or microsoft to add nic drivers to the oem$ directories as well. Been covered many times here before.
edoit: or
That *will* help for GUI-mode drivers (34 mins into install when it prompts for domain name, etc.) but won't help OP with his problem, which is that appropriate drivers don't (apparently) exist in i386.
OP, add appropriate drivers for your card into i386\system32\drivers folder. Put the .sys file into the \drivers folder as appropriate. Reboot & try again.
0 -
No server spooling
Workstation spooling
Any additional feedback would be appreciated.
Cons:
You've got to manage it on the client side, which is a PITA.
Imagine this scenario:
Users on each floor of a 5 story building are each in their own group.
Your Windows Server 2003 login script checks the group, and runs the associated batch command to map all the printers for the given users that belong to each group.
If your printers ever change, updating them enterprisewide is as easy as changing the batch script - once, not once for each and every user.
You can also manage drivers better - update a driver on the server, *one* time, and *all* clients get the updated driver.
Adding a printer on a client, if you didn't want to use batch scripts, is as easy as typing \\servername\printername, and you'll not need to add printer drivers or screw with anything else, ever.
0 -
I have an old HP Pavilion computer I bought used, for a learning toy. It now has a Cognac motherboard with a Celeron 600MHZ processor, Question, If I replace the motherboard with an Intel 810E and Pentium III processor will I have to re-install Windows XP Professional? I do not have the XP CD, but I do have the key number of the operating system that is installed on the computer, thanks to Belarc Advisor.
2nd Question, If I tried this and it would not work, could I re-install the original Cognac motherboard and be back in operation. Thanks Foz
You'll be fine if the HALs used by both are compatible and if the hard disk controllers used by both are compatible. You can't solve the HAL issue easily, and the hard disk controller issue can be resolved by pre-installing the HDD drivers for your new motherboard while your old MB is still in use.
If you couldn't boot with the new MB, just put the old one back in.
Legal users, for the most part, shouldn't need to worry about reauthorizing the computer; it should be very straightforward.
0 -
Has anyone successfully been able to perform an unattended installation on Win2k for a Multifunction Printer.
I have a dell 962. Dell does not provide certified microsoft drivers for this device. If I install the drivers before deployment of the machine and then have the client plug in their USB printer it tries to reinstall the drivers as each USB device has its own unique identifier. It cannot complete the installation as the users are locked down and the install requires admin rights.
(Bump) We've also got a locked environment - and printers aren't available during the machine build. Any information on how to allow users (as non-admins) to install drivers, even months after the intial build, would be appreciated.
0 -
I got it working with that HP format util; just had to use FAT16 (not 32 as stated with Microsoft's formatufd instructions)
So what, exactly, did you do? I used HP's util to format FAT16 as you said, then put the MININT directory in place and copied 2 files over so I finally had an NTDETECT and NTLDR file in the room of the USB drive; wouldn't boot.
??
0
: , but I didn't know if it would hurt me in the long run 
. Please anyone and every one answer as I need every ones experience with this.
We have 12 printers on our network and all have their own IP addresses. There are about 150 users using these printers in different locations at different times. All 12 printers have been installed on all the computers. We just purchased a new color printer and I need to give access to everyone. The only option I know now is to log in as either admin or myself and install the drivers and I have to do this on all 200+ computers we have. Is there a way that I can use a policy or network install to save me the headache of going from one office to another?
Unable to install network adaptors on Pentium D (dual core) in BartPE
in Windows PE
Posted
Can you isolate what's slow? Is the slow part xfering the data, or writing it? If you just xfer it and then discard the data (and don't write it locally) is it still slow? If so, you've got a disk slowdown issue. If you can't even xfer it quickly (ie you discard the data and don't write it - and it's still slow) then that's an ethernet NIC issue.