cluberti

This happens because a PCL print driver must convert the PDF file to a format it understands (and it's converting the whole document to a bitmap...), thus causing the huge baloon in size from the original PDF to the actual print job file before it's spooled and printed. PostScript print drivers shouldn't cause this type of problem, however, as they should be able to handle the PDF natively - however, there can be differences in the techniques used by the print vendor in the PDF formats they expect and the format the PDF was generated in by Adobe, causing other types of issues when printing PDFs. You could try unchecking the "Enable Advanced Printing Features" option on the print queue properties to print RAW instead of EMF for PCL drivers to disable the advanced output EMF can provide, but you'll still have the bmp conversion (just a smaller bmp file, without the extra EMF data) and the slowness to spool if the queue is local. The files can get even larger if the PDF file has embedded fonts There's not much more you can do other than deal with it, as this is an issue with the print driver handling the PDF format - it's never pretty.

From the help: So, try this: psexec \\vxp1 -u admin -p admin1 -i C:\Windows\System32\cmd.exe

Strip it down to bare-bones - 1 known-good video card, 1 stick of known-good RAM, processor, and a known-good hard disk - nothing else. Does it still fail then?

When you have /debug in your boot.ini, you also need /debugport=COM1 (for COM port debugging) and a null-modem cable attached to the COM port at one end, and another machine running kd, cdb, or windbg at the other end listening on the COM port. If the machine freezes when you have /debug in your boot.ini, that means you DID hit a breakpoint and a debugger and COM port attached would have shown it to you (it's frozen because the breakpoint was hit, and the Windows kernel broke in to allow the remotely attached debugger to run commands). If the machine reboots without /debug, then I would suggest you configure for a complete memory dump and disable the automatic reboot - if a box boots in safe mode but not in regular mode, it's a kernel driver issue 99.999% of the time.

179221 - How to Limit User Access to Local Computer or Hard Disks with Internet Explorer 4.01 http://support.microsoft.com/default.aspx?...kb;EN-US;179221 It's for IE 4.01, but most of this article should still apply.

Consider downloading the Backing Up and Restoring Windows Small Business Server 2003 document from the source.

What exactly are you trying to do? Are you simply trying to get networking to work, or are you doing something more specific (like guest/host file sharing)?

Without a domain, you will need to add the user accounts (and passwords) of every other account on the other machines to this box. Computername\Username will not work - you'll need accounts/passwords on all of the machines on the network, including the file server.

It stinks for people it happened to, hopefully you've been able to recover. Always be wary of free software from commercial vendors .

IRQL not less than or equal errors usually mean a driver on your system executed a command at an invalid IRQL level, or, caused a pageable operation at an IRQL of 2 (DPC Dispatch) or higher. These are ENTIRELY driver errors unless you've got a bum overclocked CPU or bad RAM (which you seem to have already checked) - at this point, I'd check all of the drivers on your machine (video, audio, network, antivirus, firewall, antispyware, whatever else you have installed that has kernel-mode drivers) and make sure you're running the latest versions of the vendor's product/drivers, and that they're WHQL certified (for hardware drivers) if at all possible.

Disable Windows Defender: http://www.simplehelp.net/2007/02/15/how-t...en-vista-boots/ UAC prompts: http://blogs.msdn.com/tims/archive/2006/09/20/763275.aspx

First off, IE is not able to directly edit a process space other than it's own, so you're talking about sending a WM_ message to explorer to do this, which I can honestly say I've never seen a base IE install do this. It's more likely you had an add-on in IE that sent the message, if in fact it even came from IE at all (explorer would be able to do this, so an add-on running in explorer.exe is much more likely). If you disable all non-Microsoft boot/startup items via Autoruns and disable all non-Microsoft shell extensions in explorer via ShellExView and reboot, does the problem continue? Also, does it happen in Safe Mode w/Networking?

It could be a BIOS issue with large drives - is there a BIOS update for your HP that you could upgrade to?

Here are the bluetooth Win32 API functions: http://msdn2.microsoft.com/en-us/library/aa362927.aspx If you want to actually control the state of the radio, you'll have to contact the device vendor themselves to see if there is a way to programmatically control the radio state, as there is no API to do this via the Win32 API.

If you did a clean installation of Windows onto that 40GB drive, installed nothing else (including drivers), and the problem continues, I'd start by replacing the drive. After the POST but before the splash screen is when the BIOS is "handing off" to the bootloader, and that's when the kernel is being loaded. If it takes that long and it isn't a driver problem, then I'd suspect a bad drive, yes.

If money is no object, the XServe is a really good file server in a small package. That said, you're not really paying for much above and beyond a plain-jane server you can get to run Linux or BSD anywhere else other than the niceties of firewire and a good-looking package. If you're a Mac shop and you're comfortable with OSX, the XServe is a nice product. If you fancy yourself smart enough to buy a comparable x86 or x64 piece of hardware and install Linux or BSD, you'll get pretty much the same performance and interoperability out of that box too (remember, OSX is ultimately a BSD underneath with a very pretty skin and some Mac-ish smarts on top). Ultimately, it depends on how much you want Mac hardware at the back-end of your shop - if you run Mac's, an XServe is a no-brainer if cost isn't a problem.

Hehe - always glad to be of service, even when I don't mean to .

What happens if you disable the service, reboot, and then re-enable and start the service? Can you stop and restart it then?

Are you trying to install MSI 3.1v2?

Agreed - in fact, even with multiple physical RAID arrays, I generally mount the first as the "storage volume", D:, and then all other arrays as mount points inside this volume. It's also a preferable setup in Cluster and near-line storage as well, as defragmenting or running chkdsk (heaven forbid) doesn't affect the whole volume, just the mount point, reducing possible downtime. One other drawback to the small partitions people make on C: is that they generally don't leave enough room for a pagefile on that drive that's at least the size of RAM in the machine - if the box ever goes south and you need to analyze it, you CAN'T get a memory dump without a pagefile on C: that's at least 2GB (kernel-only) or RAM+64MB (full dump, preferable). The moral of the story is to use the disk space you have, and partition only when ABSOLUTELY necessary. Oh, and use RAID10 .

One other thing to note that isn't RAID-related, but it is related to large volumes - assuming the Windows server hosting this volume is an x86 server, 900+GB of storage will start to consume large amounts of kernel paged pool due to prototype PTE tracking files and folders on the volume, as well as MFT and volume bitmap and folder bitmap cache size, which are all allocated out of kernel paged pool. Especially on large volumes where VSS snapshots are enabled, you can easily run your box out of paged and nonpaged pool by attaching volumes that large - if you think this volume may fill over 500GB or so in the future, especially if you want to enable VSS (and you probably do, it really is a boon to have users able to restore their own files!), consider strongly installing Windows 2003 x64 on the server rather than x86 if the hardware is x64. Just a side-note admins don't think about before putting multi-hundred gigabyte and terabyte arrays on x86 boxes...

From a batch file. From a VBScript. What you do with these is up to you .

Not sure if you've seen this page yet or not, but it should give you an idea about what licensing options are available for SBS 2003. As to where to purchase them, they should be available from most VARs in your area, and also online. 5-packs are pretty common, although if you go through a larger vendor they may be able to give you a larger pack (discounts may or may not be applied, though). As to the printer question, I don't believe you need a device CAL for printers, just for clients using the server that hosts the print queues.

You could also consider running filemon while you see the file growing to determine who's writing to it.

Windows Fax and Scan application comes with Vista Business/Enterprise and Ultimate only.