quya

I'm sorry if my any behavior makes you feel uncomfortable. I don't think we must have reason in helping others, just like other people provide with us this information. That depends on your willing. I admit I posted this info & files on other sites, because I want to share them with other people. I'm a newbie though I came here since 2003, I learnt a lot from this site and other sites, so what I posted are from many different sites, not 100% copied from this site, this site is one of my most favorite sites. I do want to contribute something to this project, so I PM you before I was willing to provide you with my script for you test, unfortunately, you did not answer me. You said you "Nope, not a word" in Chinese in you post#512 of this topic, now you admit "my Chinese isn't really that good... but one thing is obvious...", I'm really confused. To be frank, these info & files are not very useful for me or other individual, especially for those files I mentioned which are very rarely used, because in most case they only need one set of them, I collect them in case that some people need them so I can share them and let more people get benefits from them. If other guys need them, I'm willing to open them instead of hiding them. If you help me I will be happy, if you don't I won't mind it, but please be kindly free of prejudice against me. Thanks.

FreeStyler, Please, Please do me a favor to tell me where I can get the following OEMBIOS files. EPSON 74163373 HITACHI BE5CE5BD Mitsubishi 71631112 MOUSE Computer MCJ Co,.Ltd DEBD653E Seanix/Cicero Seanix B7FC8D93 SOTEC SOTEC E0766DE2 Targa TARGASYS D0F94E0D TIME COMPUTER Time Computers, Time Computer 7EB9D890 SHARP SHARP 8432EB94 JVC JVC_MPXP B3F88133 ASUS 2411858C Thank you very much.

As Bezalel said: "there are performance and security penalties if this range is unnecessarily large" I met a probelm when I use simple oemscan.ini. It scanned "TOSHIBA" SLP in a SONY computer, becuase this computer has THSHIBA bluetooth hardware, and it found "TOSHIBA" within the range 0x000E0000:FFFF. Actually, "TOSHIBA" SLP is located in the range 0x000F0000:FFFF. Please note that the default range of oemscan.ini is 0x000E0000:20000 if no range specified.

So, for Tektronix I should write the range as follows, right? By the way, where can I get this technical information you mentioned.

Please see my oemscan.ini as follows. However, I don't know some SLPs range exactly, becaue they are maked as "." in oembiso.dat, so I enlarge their range. For example, AMOI, Tektronix, JVC, SHARP. ; OEMScan v1.4.1 by Jeremy (xehqter) ; ; Gateway / eMachines OEMBIOS Files CRC32 = C86378C7 & A04597C6 ; SLP = Gateway,EMACHINES ; ; CRC32= A04597C6 [Gatewa] PATH=".\GatewayA\" RANGE="0xFE840:20,0xF0A0B:100,0xF0EF6:100,0xE0840:20,0xEFD3A:20,0xF2EBA:20,0xF0DB3:20,0xF1036:20,0xE49C1:20,0xE3024:20,0xF307F:20,0xF28AC:20,0xF2B23:20,0xF3D37:20,0xEBA1C:20,0xF00F2:20,0xFDE11:20,0xF3AA6:20,0xF9577:20,0xF32F0:20,0xE46C0:20,0xF330B:20,0xF3110:20" ; CRC32 = C86378C7 [Gateway] PATH=".\GatewayC\" RANGE="0xFE840:20,0xF0A0B:100,0xF0EF6:100,0xE0840:20,0xEFD3A:20,0xF2EBA:20,0xF0DB3:20,0xF1036:20,0xE49C1:20,0xE3024:20,0xF307F:20,0xF28AC:20,0xF2B23:20,0xF3D37:20,0xEBA1C:20,0xF00F2:20,0xFDE11:20,0xF3AA6:20,0xF9577:20,0xF3200:20,0xE46C0:20,0xF330B:20" ; CRC32 = C86378C7 [EMACHINES] PATH=".\GatewayC\" RANGE="0xF0000:FFFF" ; ; Dell OEMBIOS Files CRC B6F0EEFD ; SLP = Dell System, Dell Computer, Dell Inc ; [Dell System] PATH=".\Dell\" RANGE="0xFE076:10,0xF49A9:10,0xFE05E:10" [Dell Computer] PATH=".\Dell\" RANGE="0xFE840:10" [Dell Inc] PATH=".\Dell\" RANGE="0xFE838:18" [Dell Quanta] PATH=".\DellQ\" RANGE="0XFE827:21" ; ; Sony OEMBIOS Files CRC32 = 376E13C7 ; SLP = Sony Corporation ; [Sony Corporation] PATH=".\Sony\" RANGE="0xFFF80:70,0xFDFC0:40,0xFE800:80" ; SAMSUNG OEMBIOS Files CRC32 = 904CF15A ; SLP = $SAMSUNGPC ; [$SAMSUNGPC] PATH=".\SAMSUNG\" RANGE="0xFE710:100" ; ASUS OEMBIOS Files CRC32 = B20C65BF ; SLP = ASUS_FLASH ; [ASUS_FLASH] PATH=".\ASUS\" RANGE="0xFC000:3FFF" ; BenQ OEMBIOS Files CRC32 = B55014F0 ; SLP = BenQHub ; [BenQHub] PATH=".\BenQ\" RANGE="0xFFE00:1FF" ; MSI OEMBIOS Files CRC32 = CDB82950 ; SLP = MSI-2831-MS, MSI-PenNote, MSI-PC ; [MSI-2831-MS] PATH=".\MSI\" RANGE="0xFFF70:10" [MSI-PenNote] PATH=".\MSI\" RANGE="0xFE6D0:10,0xFFF70:10" [MSI-PC] PATH=".\MSI\" RANGE="0xFFF70:10" [AMOI Electronics CO.,Ltd] PATH=".\AMOI\" RANGE="0xFE700:104" [MEI_CF] PATH=".\Panasoni\" RANGE="0xFE600:6" [SHARP] PATH=".\SHARP\" RANGE="0xFFFC0:3F" [LG Electronics] PATH=".\LG\" RANGE="0xFE000:200" ; Actebis OEMBIOS Files CRC32 = 9433FB11 ; SLP = Actebis:SAM#451B ; [Actebis:SAM#451B] PATH=".\Actebis\" RANGE="0xFC000:1000,0xFD000:1000,0xFE000:1000" [Tektronix] PATH=".\Tektroni\" RANGE="0xFBEC6:4139" [JVC_MPXP] PATH=".\JVC\" RANGE="0xFEC60:139F" ; ; HP / Compaq OEMBIOS Files CRC32 = 06D652A4, CD4E1902 ; SLP = Compaq, Hewlett, HP Pavilion ; ;CRC32 = CD4E1902 [Compaq] PATH=".\HPQ\" RANGE="0xE0000:FFF0,0xF0000:FFF0" ;CRC32 = CD4E1902 [Hewlett] PATH=".\HPQ\" RANGE="0xE0000:FFF0,0xF0000:FFF0" ;CRC32 = 06D652A4 [HP PAVILION] PATH=".\Pavilion\" RANGE="0xF0000:FFFF" ; ; Lenovo OEMBIOS Files CRC32 = 5237B729 ; SLP = LENOVO ; [LENOVO] PATH=".\Lenovo\" ; LEGEND OEMBIOS Files CRC32 = 7B06BD13 ; SLP = LEGEND Dragon ; [LEGEND Dragon] PATH=".\LEGEND\" RANGE="0xF0000:FFFF" ; ; IBM OEMBIOS Files CRC32 = D7A77612 ; SLP = IBM CORPORATION ; [IBM CORPORATION] PATH=".\IBM\" ; ; Toshiba OEMBIOS Files CRC32 = A16F9D62 ; SLP = Toshiba ; [TOSHIBA] PATH=".\Toshiba\" RANGE="0xF0000:FFFF" ; FUJITSU OEMBIOS Files CRC 9CF90CA8 ; SLP = FUJITSU-PC ; [FUJITSU-PC] PATH=".\FUJI\" ; FUJITSU OEMBIOS Files CRC 10045CFA ; SLP = FUJITSU SIEMENS, FSC SYSTEM, FSC SERVER ; [FUJITSU SIEMENS] PATH=".\FUJITSU\" [FSC SYSTEM] PATH=".\FUJITSU\" [FSC SERVER] PATH=".\FUJITSU\" ; FUJITSU OEMBIOS Files CRC D2D64C41 ; SLP = FUJITSU, SIEMENS, PRIMERGY ; [FUJITSU] PATH=".\FUJITSUS\" [SIEMENS] PATH=".\FUJITSUS\" [PRIMERGY] PATH=".\FUJITSUS\" ; HEDY OEMBIOS Files CRC32 = 162C7931 ; SLP = HEDYCOMPUTER ; [HEDYCOMPUTER] PATH=".\HEDY\" RANGE="0xF0000:FFFF" ; Founder OEMBIOS Files CRC32 = 3A0C0121 ; SLP = Founder PC ; [Founder PC] PATH=".\Founder\" RANGE="0xF0000:FFFF" ; GREATWALL OEMBIOS Files CRC32 = 47E62C15 ; SLP = GREATWALL ; [GREATWALL] PATH=".\GREATWAL\" RANGE="0xF0000:FFFF" ; Acer OEMBIOS Files CRC32 = 717B6EF3 ; SLP = AcerSystem ; [AcerSystem] PATH=".\Acer\" RANGE="0xFE000:2000,0xF0000:E000" ; Acer TravelMate OEMBIOS Files CRC32 = 700A8481 ; SLP = TravelMate ; [TravelMate] PATH=".\TravelMa\" RANGE="0xF0000:FFFE" ; TSINGHUA TONGFANG OEMBIOS Files CRC32 = 7870B3C6 ; SLP = TSINGHUA TONGFANG COMPUTER ; [TSINGHUA TONGFANG COMPUTER] PATH=".\TSINGHUA\" RANGE="0xF0000:FFFF" ; Haier OEMBIOS Files CRC32 = A94BE5ED ; SLP = HaierComputer ; [HaierComputer] PATH=".\Haier\" RANGE="0xF0000:FFF0" ; TCL OEMBIOS Files CRC32 = D99F7B12 ; SLP = TCL123 ; [TCL123] PATH=".\TCL\" RANGE="0xF0000:FFFF" ; NEC OEMBIOS Files CRC32 = E32D3612 ; SLP = NECC_, NEC-PC, NEC Computers, NEC_Product ; [NECC_] PATH=".\NEC\" [NEC-PC] PATH=".\NEC\" RANGE="0xF0000:FFFF" [NEC Computers] PATH=".\NEC\" RANGE="0xF0000:FFFF" [NEC_Product] PATH=".\NEC\" RANGE="0xF0000:FFFF" ; NEC OEMBIOS Files CRC32 = 678752DC ; SLP = NECc_, NECC1, NEC-PC ; [NECc] PATH=".\NECC\" RANGE="0xF0000:FFFF" [NECC1] PATH=".\NECC\" RANGE="0xF0000:FFFF" [NEC-P] PATH=".\NECC\" RANGE="0xF0000:FFFF" ; Hasee OEMBIOS Files CRC32 = 1C1187CB ; SLP = Haseecomputer ; [HASEECOMPUTER] PATH=".\Hasee\" RANGE="0xF0000:FFFF" ; DIXONSXP OEMBIOS Files CRC32 = 221C8416 ; SLP = DIXONSXP ; [GIGABYTE] PATH=".\Gigabyte\" RANGE="0xF0000:FFFF" [DIXONSXP] PATH=".\DIXONSXP\" [BIOSLOCKFUNCTION ELITEGROUP] PATH=".\ELITEGRO\" RANGE="0xF0000:FFFF" [emaxs] PATH=".\Emaxs\" ; Equus OEMBIOS Files CRC32 = 0D59FC53 ; SLP = Equus ; [Equus] PATH=".\Equus\" [Lan Plus] PATH=".\LanPlus\" [MAXDATA] PATH=".\MAXDATA\" RANGE="0xE0000:FFFF,0xF0000:DFFF" ; MEDION OEMBIOS Files CRC32 = 06485F9D ; SLP = MEDIONPC, MEDIONNB ; [MEDIONPC] PATH=".\MEDION\" RANGE="0xF0000:FFFF" [MEDIONNB] PATH=".\MEDION\" RANGE="0xF0000:FFFF" ; SYSFIC OEMBIOS Files CRC32 = 15367043 ; SLP = SYSFIC ; [SYSFIC] PATH=".\SYSFIC\" RANGE="0xF0000:FFFF" [SNC302EEH] PATH=".\Systemax\" [TRIGEM] PATH=".\TRIGEM\" RANGE="0xF0000:FFFF" [iQon.ie] PATH=".\iQonie\" [vpr Matrix] PATH=".\Matrix\" RANGE="0xF0000:FFFF" ; Micro OEMBIOS Files CRC32 = AA944D37 ; SLP = powerspec, WinBook ; [powerspec] PATH=".\Micro\" RANGE="0xF0000:FFFF" [WinBook] PATH=".\Micro\" RANGE="0xF0000:FFFF" [HIGRADED] PATH=".\HIGRADED\" [alienware] PATH=".\Alien\" [americanfuture] PATH=".\AMERICAN\" RANGE="0xE0000:FFFE,0xF0000:FFFE" [EPSON] PATH=".\EPSON\" [HITACHI] PATH=".\HITACHI\" [Mitsubishi] PATH=".\Mitsubis\" RANGE="0xF0000:FFF0" [MCJ Co,.Ltd] PATH=".\MOUSEC\" [OQO Inc/Zepto/(jja)] PATH=".\OQO\" [Seanix] PATH=".\Seanix\" RANGE="0xF0000:FFFF" [SOTEC] PATH=".\SOTEC\" RANGE="0xF0000:FFFF" [TARGASYS] PATH=".\Targa\" RANGE="0xF0000:FFFF" [Time Computer] PATH=".\TimeC\" RANGE="0xF0000:FFFF" I would appriciate if anyone can provide me with the oembios files as follows.

Nice Job. By the way, do you speak Chinese? Because you mentioned Chinese website here.

Hi Greenmachine, I made a test, I integrate SP3 with IE7 (at T13) into installation CD. After installation, I add the following information into reg. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Setup\7.0\WU] "ForcePostUpdateInstall"=dword:00000001 And immediately I install KB947864, unfortunately it still failed just like before. Only re-installing IE7 can solve this problem. I did not test to install IE7 and KB947864 all at T13, but I think there is no much different than what I did, any comments please. Thank you. By the way, KBxxxxxx /ER, what's mean for switch "/ER", thanks. I only use switch /q /n /z, should I use other switchs?

Is it possible to use *.reg /s file instead of reg.exe to save the space? I also doubt if the reg.exe have been already extracted at T13? So we don't need to copy it to that folder again?

Thanks a lot. I will try that method later. If it works fine, it is obvious a better way.

I noted many people have a problem to install KB947864 unattended with SP3. Now I got a stupid way and run it successfully on my virtual machine. 1. Integate IE7 with svcpack to run it on T13 2. Run IE7 again and KB947864 on GuiRunOnce Any better way, please let me know, thanks. Related topic: http://www.msfn.org/board/SP3-and-KB947864-t116716.html

Even I reboot between IE7 and KB947864, KB947864 still fail to install, unless re-installing IE7. Many people have this probelm, is there any way to fix it?

I have the same problem. Is there any better way than re-installing IE7?

Sonic, Microsoft said that we need muti-hofixes if installed muli-versions for MSXML, but KB927978 is a full installtion for MSXML 4.0 SP2. So why we still need KB924191 for MSXML 3.0? Actually I have not seen this hotfix in my update list after a fresh installation with KB927978 slipstreamed. Could you explain more about this, thanks. Another question, if proved we still need KB924191, how can we get rid of MSXML 3.0? So we can definitely delete KB924191 from our unattended CD. If I still have space, I don't care about this hotfix. The fact is that too many hotfixes make me difficult to make a 700M CD. The Microsoft should release a roll-up hotfix just like they did before.

KB924191 is replaced by KB927978, Right? I make a fresh install and only install KB927978, selfupdate don't display KB924191. However, other guy said KB924191 is also needed, anyone else can clarify it?

Thanks for your guide. Now I know this file should be repacked, however, there is only English version, I will try to unattend-install My Chinese version after 1st boot, to see whether it can work.

I can not post a new one in this forum, so I just add a reply, sorry. 1. I agree with heathy, hope the future version can allow us to customerize the pack. 2. I have not updated this driverpacks for a long time, recently I download the new version DPs_BASE_6061 and DP_MassStorage_wnt5_x86-32_6031, I have some questions about them, is there anyone can help me? Thanks. A. During slipstreaming (method 1), it did not revise my dosnet.inf and txtsetup.sif, why? If using method 2, it only revised txtsetup.sif and winnt.sif. Is this normal? B. It won't copy any *.sys file to \I386 folder, why? C. It seems that DPs_fnsh.CMD do nothing about MassStorage pack. Since the previous version will do what I expect, but the new one won't, so I'm very confused.

I failed. I can do with MSN messenger 6.1 or 7.5, but with new version MSN Live messenger, I can not install it unattended. "MsnMsgs.msi /q " can work after Windows XP installtion, but it doesn't work in GUIRunonce, nothing installed at all, no error report. Anyone can tell me what happened and how to install it. Thanks.

In the most case, you virtual PC can accept you OEM key if you use right version, but it is very hard to activate it. Because every XP OEM version also check the bios information when activation, for example your HP computer, there must be "Hewlett-Packard" of Manufacturer Name located in "System" and "base board" in the bios. However, it is very hard to modify your bios information for virtual pc. Even you can change that information in your real pc, it is illeagal. So just use virtual PC to verify if your own unattended XP can work properly, not to try to avtivate it. Also, it is no use to alter setupp.ini only between simple XP Home version and pre-install XP Home version, at least you should alter other 4 files. I can not say more, as ZaFord said, it is a risky topic.

I have the full version provided by my laptop manufacturer. Is there a certain file or series of files I need to add to the unattended XP CD? You may use a OEM key for VOL version or vice versa. Or you use a key of XP Home Version for Professional version.

And now for some good news... If you take the following 13 files from the cabs downloaded from the image above, compress them and put the files in your i386 folder (replacing the old ones), Windows Update v5 works as if everything was installed. cdm.dll iuengine.dll wuapi.dll wuau.adm wuauclt.exe wuauclt1.exe wuaucpl.cpl wuaueng.dll wuaueng1.dll wuauhelp.chm wucltui.dll wups.dll wuweb.dll <{POST_SNAPBACK}> I noted that there are 7 cat files, should we put them in \i386\svcpack or other place and prevent the error messgae in setuperr.log? As you know, if any error be logged in setuperr.log, it looks not professional. Are those cat file really needed?

Bâshrat: Thank you very much for your answer & understanding my broken English. 1) Understand. Anyway, you'd better tell the user how to use it, or it's useless to put it there, at least I didn't know before. 2) I were also not sure if it worked if put the drivers in \$oem$\DP with *.sy_ format, now I believe it does, since many people use your new version and no bug report about it. I'm just curious about it. Just compress them and no script need to tell it how to uncompress? I know Windows XP can deal with it, she can use her own way to let the "sy_" to "sys", "dl_" to "dll", etc., because she put some information in TXTSETUP.SIF or other files. However, the drivers are from the third parties. By the way, for some "in_" files, who know their original extension are "inf" or "ini", XP know but I don't know. Bâshrat: Thank you again. PS. You are definitely a professional programmer, because programming in DOS need a lot of skill, While programming with advaced language is easy as toy bricks piling.

Thank you two anyway. However, I just want to know: 1) Why put cmdow.exe in that directory? Someone will confused about if it is a origianl file of XP, obviously it can be put in anywhere. I have not found it used in method one, maybe in method two. It is better to regard it as a seperate file from XP or your driverpacks. Thank you to tell me the usage of it. 2) In previous version, actually *.sys have been already compressed in I386 directory, I just wonder why saved them in \$oem$\DP in different fomat at that time. I know they are compressed and how to compress them. Why people did not do so before, Negligence? or must to do so before V5.02? Thank you for your reply.

Hi, Anyone can explain to me? Thanks. 1. I found a file called cmdow.exe located in \I386\system32, but I can not find where it should be applied. Why? Can I delete it when burning? I doubt it is a temp file when slipstreamed. 2. In the previous version, the drives files in \$oem$\DP\ save as *.sys not *.sy_. Why? Does the new version use new method, so we can save them as *.sy_ now, or it can be originally saved as *.sy_ but we did not do so before? I knew the *.sy_ is a compreesd one of *.sys.

When I install windows XP sp1, I add some in winnt.sif as follows [Components] fp_extensions = on iis_common = on iis_doc = on iis_inetmgr = on iis_www_vdir_printers = on iis_www = on It works, but it does not work with SP2, is there any way to make it? Thanks.

Anyone know how to do that? Because I only want the core codec, it's about 2M. I want to get rid of Divx Player, it occcupies 4M and I never install it. Though I can choose whether to install it or not, I prefer to remove it from installation program to save room. Anyway, I do not want to remove the config file and register file. I have a rip version handy, but without the above two files. Any help will be appreciated.