likuidkewl

Are you still stuck on the Winbom.ini error? If so this is due to the drivers for your network card not being supported. I also tried to use VMware and the network error you mentioned was there for me also, But when I burned it to a CD it was fine. The only ones it has issues with are the Intel network adapters and the VMware network adapters, it has never bothered me enough to see how to fix it in VMware because I know it works outside. I have also found that when building an ISO from say Longhorn's older builds with the same file structure as XP, I also sometimes get this error. My advice to you is to be safe and extract your files with WinRAR, no problems for me ever, get Bart's tool for extrating boot files(from the pre-built ISO), and then reburn it with CDimage and the extracted boot image file.

Try again with new media if available.

What version are you using? Also try to rebuild your ISO.

I see everyone is trying to stay on topic. Anyhow, my question is where does the winnt.sif file get created and placed? And for those of you worried about reburning the CD all you would have to do is write a little script for Diskpart to clean the HD and then create a small partition of at the most 8mb to keep the rest of the hard drive partitioning clean and smooth. <Don't quote me on partition sizes below I just made them up> SifPrep.cmd diskpart /s %systemdrive%\<your folders>\diskpart.txt format Q: /fs:fat32 /q /v:CRAP /y format c: /fs:ntfs /q /v:Install /y Diskpart.txt example script DISKPART SEL DIS 0 CLEAN CRE PAR PRI SIZE = 8 ID = 12 ASSIGN LETTER = Q CRE PAR PRI SIZE = 20480 (remember just an example) ACT ASSIGN LETTER = C EXIT After here all you would have to do is point your winnt32.exe to the place where you stored the winnt.sif, here it would be Q:\winnt.sif Easy

That line above is for CDimage from Microsoft. 2.27 is old released in 1996 I believe. Also please becareful how you post on the boards here no warez/crackz etc. But as stated above that file is CDImage from Microsoft just download the file and run cdimage.exe and you will see all of the options you can pass to it. HTH BTW the version above is 2.47

As an update, all of the previous builds prior to RC1 have now been removed from WindowsBeta. fyi

This email was received today at 2050EDT, from MS OEM for Partners News letter. The following excerpt discuss the release date party. Sorry if old news but I hadn't seen it before. Coming Soon!

Good place for info on what chips do what: http://www.xs4all.nl/~ganswijk/chipdir/ Specifically check these links out: http://www.xs4all.nl/~ganswijk/chipdir/ext/course.htm

First off get yourself some AutoCad! OK quick rundown, There are two types of circuts Digital and Analog, Digital is really easy +5 = on, 0 = Off, kinda like binary. now this should be really easy but alas it will probably be more of a pain becasue you are not just doing the ASM you are building the whole thing, so what you would need is to figure out what you input is going to be, rather how will it be delivered. ex. A knob when turned CCW will move the paddle left, ok easy 0vdc = left and +5vdc will = right or a CW turn on the knob. So the knob will have a pin on on one side which when turned left(CCW) will ground out the +5vdc, causing the +5vdc to go to 0vdc or ground. Ok so now from the IC chip to the LCD, this could get tricky so don't quote me on this, depending on what LCD you use you could need a bunch of different voltages, ex. +12vdc, this is where the programming of the IC chip(s) comes into play. Voltages to the LCD, Data to the LCD, etc. I have never built anything from the ground up, except a wireless antenna. So as you can see some research is required. Hope ths helped!

Also from what I heard it was garbage anyhow, alot of people said they had trouble running .exe's for gods sake..

Whats funny is SP2 2111 isn't even listed there!

Thing is you need to find the board you are going to use then figure out how many pins and how much space you need, etc. Do you have some idea of what the layout of the board is going to be? If you have some schematic diagrams you can email them to me and I will try to help you out. *BTW I do this for a living* //Editted fot major spelling/grammatical errors //

That is a good firewall, but in order to run at its full potential the server itself should not be the ISA server. I do believe he is meaning client side firewall. But must say I stand by ISA server 2000, the only thing I feel lacks is the reporting options.

Cheap EEPROM http://www.mouser.com/

Go to another computer and then go here http://vil.nai.com/vil/virus-4d.asp and then dl the command line virus scanner, burn it to a CD(this is so no virus can infect it), pop it your computer and type in %virusDir%\Scan.exe /AD /ALL

Don't double post, look here for the layout of the Unattended disc.

Yeah I figured as much. **** it. Probably will ot be up until tomorrow too. Argh...

Can anyone else not login to http://www.windowsbeta.microsoft.com/ ?? Or is it just me?

http://unattended.msfn.org/files/CDImage_Pro.zip

How to do what? If you mean make the executable boot @ PE start then you just modify your %systemdrive%\PEfolder\I386\system32\setupreg.hiv in this key: setup\cmdLine REG_SZ cmd.exe /k startnet.cmd <-- Just change it to your exe.

A common misconception, linksys cards do not have any cisco chips in them. All they do is put there name on the box.

Have you tried PEshutdown.exe? You can get it here: http://home.t-online.de/home/520085154509

http://www2.us.freebsd.org/releases/5.2.1R...386.html#AEN815 It should be one of these chipsets if not, I know there is no support in *Nix period for the broadcom chipset version.

I know there is a good article on doing it with FreeBSD, and also another good article on how to dual boot BSD and Windows. Hold on I'll find them real quick. //EDIT#// Configuring a FreeBSD Access Point for your Wireless Network http://www.samag.com/documents/s=7121/sam0205a/sam0205a.htm Dual booting issues http://www.informit.com/articles/article.a...=32084&seqNum=4

Direct from the CD: MSI_FAQ.txt ******************************************************************************Symantec AntiVirus Corporate Edition 9.0 MSI_FAQ.TXTCopyright 2004 Symantec Corporation. All rights reserved. March 2004****************************************************************************** This file is a list of the most commonly used MSI commands for Symantec AntiVirus and Symantec Client Security. For a complete list of commands, properties, and features, see the Symantec Knowledge Base. BASIC MSI commands------------------/QN - Quiet No UI/QB - Quiet Basic UI/L*V log.txt - full verbose logging to file log.txt BASIC MSI properties--------------------REBOOT=REALLYSUPPRESS SAV properties--------------INSTALLSERVER= (1 = Server, 0 = Client, Default is client) SERVERGROUPNAME= (New or prexisting servergroup) SERVERGROUPPASS= (New or prexisting servergroup password. The default is symantec) NETWORKTYPE= (1 = Managed, 2 = Unmanaged, default is Unmanaged) SERVERNAME= (preexisting SAV Servergroup) RUNLIVEUPDATE= (run LiveUpdate during install = 1, do not run LiveUpdate=0, default is On) ENABLEAUTOPROTECT= (1 = ON, 0 = OFF, default is On) INSTALLDIR= (Install target directory, default is C:\Program Files\ Symantec AntiVirus) SERVERPARENT= (e.g. SERVERPARENT=MySavServer)Note: For a secondary server silent install from the command line, you must set the SERVERPARENT property to the Parent server computer name. When doing a UI or Symantec System Center rollout install, setting this property is not required. SAV features------------EMailToolsNotesSnapinOutlookSnapinPop3SmtpQClientSAVHelpSAVUI Adding and removing features----------------------------To remove existing features: REMOVE=<feature1>,<feature2>,<feature3> To add new features: ADDLOCAL=<feature1>,<feature2>,<feature3>, <existing feature 1>, <existing feature 2>, etc. Note: When adding new features using ADDLOCAL, any existing features on the target computer that you want to retain must be included in the features that you are specifying. The installation will remove any features on the target computer that are not listed. Command line example--------------------This example demonstrates a silent Symantec AntiVirus Server installation. The server is named MYSAVSERVER and uses the password MYSAVPASSWORD. LiveUpdate is not run, and the server is not restarted even if its required. Sample command line: setup /s /v"/l*v log.txt INSTALLSERVER=1 SERVERGROUPNAME=MYSAVSERVER SERVERGROUPPASS=MYSAVPASSWORD RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS"