bj-kaiser

Ffirst, disable reboot on BSOD in your image. helps greatly with debugging. Second, I suspect you have different HALs between your image and that laptop.

@weEvil: yup, spooler is running, I even tried restarting it, rebooting Vista. No help. Tried removing all of the drivers (by the ways you got in the GUI, no stumbling through registry and files yet) @hansen_dk: um, why would I need the s***ty software package for a simple printer? The only idea I have right now, some old driver fubared the spooler badly or it is another Windows related problem. I'll probably reinstall Vista monday, since it doesnt make any sense to add up some more hours of digging through the system. All I have found yet related to the error message or error code is something about network printers. But both printer drivers installed were USB. oh, and to quote unattended.sf.net: Seems Vista didn't change much about that.

I got a Vista installation here that tries to deal with any print job by presenting you with a "0x0000000d" error or "could not create print job". The printers are local and USB. For the Kyocera 1030-D I already tried to install the correct drivers (Vista KX package) but it didnt help. System is Vista Home Premium SP1 Any ideas?

they are using in-band signaling in this day and age? after all the blueboxing and whatnot?

you will have a winnt.sif or unattend.txt answer file somewhere. find it and look for the [shell] section. There are the relevant settings. http://unattended.msfn.org/unattended.xp/view/web/19/#shell

sounds like you are missing the VMware hdd driver. "peimg /inf=path/to/vmscsi.inf path/to/mounted/PEimage" should do the trick

Transmission, because it came with my OS of choice.

what issues does VirtualBox have? I use it for a XP installation and it works quite well. Cant complain here..

my 2 cents on this: The only problem you might run into with any non-native (to the protocol) client is, no webcam support. Which probably is a major feature to most users.

could it be that the Linux nosedive has something to do with the rise of netbooks? I could come up with this explanation: People bought a netbook, noticed "oh crap, it doesnt look like Windows" and installed their (legit?) copy of XP on it (or Vista for the curious ones) or even returned the machines simply "because it doesn't look and feel like Windows".

using 8.10 since one day now, the upgrade went flawless, except for the fact I had to make space on "/" since I made the (wrong) assumption when I first set up the system that 5 GB would be enough for it. And I almost forgot, if you modified any system configuration files (/etc/...), be prepared for the inquisition! The upgrader will ask if it can overwrite your changes (with the option to have a look at the differences before it does so). One thing I noticed, I seem to have trouble with hibernate now, the first try after the upgrade ended with "soft lockup in CPU#0 detected", however the second try showed some error messages, but hibernation and wakeup worked. However, I haven't lost hope yet that this problem will be fixed in due time, the release is only 2 or 3 days old now. Another thing I noticed, but to my liking, is the new UserSwitcher applet, which now combines the IM status and restart/shutdown options. There may be a drawback however for some people, if you select "logout", you will be logged out. There is no "do you really want to logout? Yes/No" dialog popping up. And so far I haven't found a switch to enable such a thing. Other than that I have not found any big changes (yet). But I haven't gone around poking into the systems internals until now.

http://technet.microsoft.com/en-us/library...351.aspx#enable if I understand it right, there seems to be server-side and client-side detection mechanisms. Now the question is, where is the client-side mechanism (either pxeboot.com or bootmgr) and how do you set it up, as server-side is a no-go for your situation. edit: some more insight: http://support.microsoft.com/kb/932447/ from http://technet.microsoft.com/en-us/library/cc754611.aspx suppose you have the Boot\x86\Images folder structure, now try creating Boot\x64\Images and place the boot configuration storage (BCD) in the related folder, just that this BCD points to your x64 PE image. Not tested, but maybe worth a try.

usually those setup.exe msi-wrappers extract the msi to some temp directory. If you only provide a filename, msiexec will probably look for that in the directory of the msi file. Did you try providing the full path to the msp?

either it displays a hotkey to press during boot or you have to use driver settings or a special setup program for the NIC:

what did your commandline look like? maybe you missed a thing or two there. never mind. looks alright. weird.

I hope the properties are the same for 3.0: http://wiki.services.openoffice.org/wiki/D...#MSI_Properties about the registration box, in v2.x (and I'd guess same for 3.0) the registration data is saved in a xml file in %APPDATA%\OpenOffice.orgX\user\registry\data\org\openoffice\Setup.xcu those 2 properties in there should be interesting: ... <node oor:name="Office"> <prop oor:name="ooSetupInstCompleted" oor:type="xs:boolean"> <value>true</value> </prop> ... </prop> <prop oor:name="FirstStartWizardCompleted" oor:type="xs:boolean"> <value>true</value> </prop> ...

they will prove you wrong on that one. just saying. you know the "ntpasswd" bootdisk?

I'll just try to remember what my favorite computer magazine wrote about this matter: (or at least something along that line) I have to say I don't have kids, but looking at the conclusion above, I'd think the best way to deal with this is to find a router that allows you to block certain PCs from Internet access while you can't watch your kid and have computers that don't get locked out by that schedule password protected.

http://www.openoffice.org/dev_docs/source/sys_reqs_30.html seems you are definitely out by design.

Active monitoring makes sense on a CLEAN system. If you already suspect an infection, nowadays malware can hide from the AV or manipulate it (especially when the malware is running), as jaclaz already said. It is pretty much pointless to install AV on a compromised system. Yes, I get the idea that malware authors could be clever enough to wrap up their crap on shutdown to avoid detection by offline scanners. But to manipulate the file/memory access and whatnot of another OS, that just accesses the disk for scanning and doesnt execute files, should be pretty unlikely. However, IMO offline system scan is your best bet. and even after cleaning, good practice would be to reinstall/restore the system to a clean state.

if you already suspect the computer to be infected, wouldn't it be better to run a AV software from another CD booted operating system? Not to mention a re-installation. Avira has a boot disk for free, as far as I understand it, the download should be mostly up to date. http://www.free-av.de/en/tools/12/avira_an...cue_system.html Then there is the SystemRescueCD with ClamAV, not the best choice, but a) its free and B) you also have a clean system here. However, you would need to update the definition files. http://www.sysresccd.org/

not one to dig out old threads, but has anyone come across a windows disk imager that can read the image data from "stdin"? Because that's the only way I could imagine to use UDPcast without having to save a temporary file on some harddisk. I understand it is uncommon on windows to use "stdin", but there has to be something besides the windows version of "dd".

I can only second that. I used to use a BEFSR41, good for day-to-day surfing and mail etc. but it craps its pants around 200 connections. What happens then is that the router seems to reboot itself.

actually my idea was that you just set up your server to allow booting of Ghost, since you already paid good money on it and I suppose its working well for you. You could probably do without pxelinux, it is just that you have to figure out the bootloader file for Ghost anyway. But pxelinux adds flexibility.

http://technet.microsoft.com/en-us/magazine/cc743170.aspx after reading that I guess you want to continue using Ghost Multicast or upgrade server 2008. Because as I understand it, WDS supports multicast only on server 2008. However, WDS still provides you with the basics for PXE boot (DHCP, DNS and TFTP service). and with the wdsutil.exe you can set the network boot program (NBP or bootloader) to be anything you like. You should take a look at pxelinux. its fairly easy to set up. all you have to do is copy it to the TFTP folder and make a config for it.