Martin Zugec

Great work I will rewrite the script tomorrow, I fill finally have to try it But I wanted to ask you, if I could edit the first page of this topic, so I will always update the script there.

Ah, sorry, I absolutely didnt understand your problem, but I do now... Anyway my solution wont help you, you cant use vbscript from DOS. Dont know if you will find solution, why are you using images instead of unattended installations?

Hmmm, well, script I posted was primary used to install chipset drivers... Now situation changed: You can use Win32_ComputerSystem, property Model... I will post a script for you, but you will have to wait

Whoa, slow down One question at a time please DCCU is Dell Client Configuration Utility - it allows you to create packages, that will automatically configure your BIOS. Yes, you are right, this script will determine the PC model. It is not based on BIOS, it is based on baseboard in computer. The script is on the page I provided The most important part for you is Case "0t9369" 'Wscript.Echo "Notebook D600" funcNainstalovanieWifi("d600") funcNainstalovanieChipsetu("d600") Case "optiplex gx150" 'Wscript.Echo "OptiPlex GX150" funcNainstalovanieChipsetu("gx150") Case "00t606","02x378" 'Wscript.Echo "Optiplex GX260" funcNainstalovanieChipsetu("gx260") Case "0x1078","0r2472","0u1324" 'Wscript.Echo "OptiPlex GX270" funcNainstalovanieChipsetu("gx270") Case "0n4846","0968h","0g5611","0f7739","0g8310" 'Wscript.Echo "OptiPlex GX280" funcNainstalovanieChipsetu("gx280") Case Else Call OdoslanieMailu 'wscript.echo "Didnt find associated PC!" End Select Every model from Dell have few variations, some of them (GX150) dont have. Under every section (wscript.echo "Notebook D600") you can include any code you want.

Sure, have a look here: http://www.msfn.org/board/index.php?showtopic=48523&st=50 Post from Jun 17 2005, 09:24 PM For Dell computers you can also use DCCU for automatical BIOS configuration, I am using the same method. Let me know if this is what you are looking for.

Why HAL? Specially on Dell machines the most simple way is using motherboard product... E.g.: Wmic baseboard get product I am using this method on GX150, GX260, GX270, GX280 and Latitude notebooks

2All: Solved, Nois3 was right - you CANT use reg directly in cmdlines, instead you must include it in batch and call that batch from cmdlines. Strange behaviour, however now it is working great!

So it is launched from c:\$WIN_NT$.~LS\$OEM$...

BTW Full WMI class is Win32_QuickFixEngineering

Wmic qfe list full Is that what you are looking for?

Well, I am not using default profile. I used it before (it was already set this way before I came here), but now I want to get rid of it, because I dont know what is set and I dont have control over it. BTW I got bored trying different approaches, so I just added everything to cmdlines.txt and it worked So I will now simply remove one line at every installation and see which one was working. I will let you know where was the problem, thx for your ideas

Sybari isnt bad - I got it in one company. As I said it wasnt normal AV company - it was using multiple engines, so for example my mails are scanned through Sybari by using two eTrust engines, Norman AV engine and few others...

Media Player Classic...

Murphys Computer Laws...

California, USA?

Have a look at my blog - there is script that is repairing WU. Also try cleaning your cache. And have a look at %Windir%\WindowsUpdate.log, you will probably see some error messages there.

Hmmm, it is second AV company MS bought.... The first one (dont remember the name) will be in OneCare, Sybari was oriented more on enterprise, so looks like we will meet soon some news about it... And Sybari was specialized on Exchange integration.

I am using virtual installs... I install it on my VPC, save without changes, repair package, deploy to VPC, save without changes etc etc...

Ok, I will first answer last question Monad dont have support for remote computing - it will of course be available in final version, now it is not. Monad (current version) have only two limitation - dont support remote networking and second thing is aliases cant contain parameters. Now for the harder part - comparing CMD vs. WSH vs. Monad. Well, it wont be so hard at all Monad containt all features of CMD + WSH + much more. WSH Monad have same advantages as WSH. For example accessing WMI objects is quite simple and logical: MSH> $objBios = get-WMIObject Win32_Bios MSH> $objBios.Name Phoenix ROM BIOS PLUS Version 1.10 A02 MSH> You can using objects in Monad using cmdlet net-object, so you can do the same as in vbscript. $objShell = New-Object –ActiveX “WScript.Shell” CMD You can use everything from cmd in Monad, so there is no reason why not using MSH instead of cmd. Implementation of StdIn/StdOut is quite simple to do, so I didnt encounter any compatibility problems at all. What is the main reason to use MSH for me is that a.) in 3-5 years (according to MS) every program from MS will have support for Monad. So you could do (similar to *nix) everything from cmd. b.) it is frontend to .NET. I cannot fully work with it yet (as I am not programmer), but it is quite similar process like WMIC - but it is much more powerfull. It is just not another shell, it is shell + language + framework.

Thats not right at all Longhorn will be based on .NET. Natively based on .NET. So for MSH fans it means, that they will probably have access to .NET classes without GUI (for example MSH wont need GUI to work)... And there are many changes... WinFS is nice, but it is not neccessary. It will be pretty different from w2k/xp - the same way w2k/xp are different from NT.

Null modem cable is serial cable... Crossed serial cable... I remember times, when games were supporting "online" gaming through Null-modem

Glad we could help So it really was FQDN?

Hmmm, it is quite harder - usually using serial ports... But it is still worth learning. If you are interested, you can begin here: http://www.microsoft.com/whdc/devtools/deb...debugstart.mspx

I vote for FTP Most simple and functional solution... I am using Xbox for this purposes It is hacker-proof system...

Hmm, no Minidump... I would try to solve it through debug console and another computer rather then trying to replace every part of PC...