Nakatomi2010

I generally reconstruct my entire AIO-DVD every month to two months in order to apply Windows Updates, Bashrat updates, and Software updates... Takes about two days (10am to 6pm) to reconstruct all 9 copies of 32-bit XP...

Not sure how sanctioned request will be, but anyone know if it'll be possble to hijack Vista's Windows PE version? (From here on in I shal refer to it as Vista PE since it is vastly better IMHO)... By hijack I mean take what exists for it and apply it towards out own nefarious purposes.....

Wouldn't mind knowing the answer to this one myself...

Heh.... hmmm......

Let's not try to kill Bashrat here....

Yeah, saying nothing at all helps the thread fall off the board quicker....

http://unattended.msfn.org/unattended.xp/view/web/31/

http://www.msfn.org/board/index.php?showtopic=58410

On boot it says "Windows XP x64 Edition" like XP Home and Pro did prior to SP2.... So yeah... Otherwise go to Run>'winver'... Otherwise, Windows Key+Pause.....

Meh.... I just find it funny that two people, no doubt several hundred miles away from each other pretty much figured out the same thing using the same method without talking to each other.... But I found it first...

It LOOKS hard, but I can assure you, once you get waist deep you'll gain a wealth of knowledge and understanding of the inner workings of XP that if you're required to fix it, you'll be able to more easily than most other people....

Did you read http://www.msfn.org/board/index.php?showtopic=58410 ?

Funny you should mention that technique OCZ since sometime ago I pretty much did the exact same thing and mentioned it in the other thread... Can't remember which one, but it was pretty much the same observation... http://www.msfn.org/board/index.php?showtopic=58927&st=30

I keep wanting to say "Incorporate it into the presetup.cmd and setuporg.exe" but you can't get that far... Does this thing affect all Methods, or just the first one? (I use Method 2)

And people wonder why I dislike that company... Of course, with my last ATi issue........ You know, these video card manufacturers should probaby stick to video cards... :| Kind of a pain to stop and delete drvers during the setup process... Is there a way to trigger a deletion during the setup process? I understand that's it's not you're fault, it's poor driver design on their part, but there has to be something that keeps it more... Unattended.... Is there anyway to do the entire text setup mode through a Windows PE environment? I mean, you do a network setup through Windows PE, why can't you do a local one?

That's correct... The Text Setup (Phase where drive is formatted, and files copied) processed fine... It used the driver properly... But when the system rebooted and went onto the GUI setup phase it failed BSOD... Oddly enough, this is the same thing that happened with the nForce chipset way back, and then again more recently with this stupid VIASRAID/VIAMRAID stuff.... Seems like I always have issues with the Mass Storage drivers... I like to think I'm helping though... :| What I'M going to assume is that the OS is using the wrong drivers... ?

Does not Compute....

I'd be more than willing to test, I'm a PC Technician so I run into ALOT of computers in a week, and I use these driver packs almost everyday...

=========== PCI devices =========== PCI\VEN_1002&DEV_4370&SUBSYS_71511462&REV_02\3&267A616A&0&A5: Realtek AC'97 Audio PCI\VEN_1002&DEV_4371&SUBSYS_00000000&REV_00\3&267A616A&0&A4: PCI standard PCI-to-PCI bridge PCI\VEN_1002&DEV_4372&SUBSYS_71511462&REV_11\3&267A616A&0&A0: ATI SMBus PCI\VEN_1002&DEV_4373&SUBSYS_71511462&REV_00\3&267A616A&0&9A: Standard Enhanced PCI to USB Host Controller PCI\VEN_1002&DEV_4374&SUBSYS_71511462&REV_00\3&267A616A&0&98: Standard OpenHCD USB Host Controller PCI\VEN_1002&DEV_4375&SUBSYS_71511462&REV_00\3&267A616A&0&99: Standard OpenHCD USB Host Controller PCI\VEN_1002&DEV_4376&SUBSYS_71511462&REV_00\3&267A616A&0&A1: Standard Dual Channel PCI IDE Controller PCI\VEN_1002&DEV_4377&SUBSYS_00000000&REV_00\3&267A616A&0&A3: PCI standard ISA bridge PCI\VEN_1002&DEV_4379&SUBSYS_71411462&REV_00\3&267A616A&0&90: ATI 4379 Serial ATA Controller PCI\VEN_1002&DEV_437A&SUBSYS_71411462&REV_00\3&267A616A&0&88: ATI 437A Serial ATA Controller PCI\VEN_1002&DEV_5951&SUBSYS_00000000&REV_01\3&267A616A&0&00: PCI standard host CPU bridge PCI\VEN_1002&DEV_5A34&SUBSYS_00000000&REV_00\3&267A616A&0&10: PCI standard PCI-to-PCI bridge PCI\VEN_1002&DEV_71C0&SUBSYS_0880174B&REV_00\4&35C10ADC&0&0010: Video Controller (VGA Compatible) PCI\VEN_1002&DEV_71E0&SUBSYS_0881174B&REV_00\4&35C10ADC&0&0110: Video Controller PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&267A616A&0&C0: PCI standard host CPU bridge PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&267A616A&0&C1: PCI standard host CPU bridge PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&267A616A&0&C2: PCI standard host CPU bridge PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&267A616A&0&C3: PCI standard host CPU bridge PCI\VEN_10EC&DEV_8169&SUBSYS_151C1462&REV_10\4&4680D9B&0&18A4: Realtek RTL8169/8110 Family Gigabit Ethernet NIC 19 matching device(s) found. =========== USB devices =========== USB\ROOT_HUB\4&29DDAED&0 : USB Root Hub USB\ROOT_HUB\4&35227E8B&0 : USB Root Hub USB\ROOT_HUB20\4&31EDAC08&0 : USB Root Hub 3 matching device(s) found. I'm guessing you probably only need these two lines: PCI\VEN_1002&DEV_4379&SUBSYS_71411462&REV_00\3&267A616A&0&90: ATI 4379 Serial ATA Controller PCI\VEN_1002&DEV_437A&SUBSYS_71411462&REV_00\3&267A616A&0&88: ATI 437A Serial ATA Controller The above HWID's are NOT in the Si3112r.inf dated 2006 Also, the Si3112r.inf dated 2004 appears to have mroe HWID's then the one dated 2006.... I've created a 'Test Chamber' which I use to put in components that need testing and let me make the images quicker, so depending on the modifications I can normally had a test subject in about an hour.... It honestly seems like the file dated 2004 supports more devices... In fact using DiffDoc I can see that MOST of the changes in the one dated 2006 are entries removed from the 2004....

Suppose the irony here is that I spent a good chunk of effort into figuring out the VIASRAID/VIAMRAID thing (For myself anyways), and the first board I really get to test out all this new stuff on is an MSI RX480 Neo2, whic uses Si3112r SATA drivers.... Got a BSOD on GUI boot.... What are the differences between the two 3112r's you included in the pack? (D/M/S/5, and D/M/S/5/A)

Figured I'd make a reply to get a little more attention... The problem is solved... The 2006 Symantec Recovery disk must use a newer version of Windows PE built off of the x64 code base, as there are references to the AMD64 directories... The solution was to take a boot sector from an x64 CD and relabel ONLY the i386 portion of it to something else, in my case 'SYM1'... Then you need to get the cracked setupldr.bin from the stickied post above and change ONLY the i386 references (7) to the same as above, so again in my case that would be SYM1, DO NOT change any of the AMD64 references..... Not sure how many of you people will benefit from this, but I thought I'd let you folks know how it's done because this is the first PE I've personally run into which required a similar method to x64 XP...

I've integrated Symantec's Norton Systemworks 2005 Reocvery CD into my Multi-Boot DVD, however I just recently got the 2006 verions (Free after rebates, figured what the hell I use Ghost often) and when I do the same thing I did before it says NTLDR is corrupt or missing.... The BIGGEST difference I can see is that there's a setupldr.exe and setupldr.bin..... I was gonna use the setupldr.bin from my other version.... Any thoughts as to what's up with this one? What's sod different, shy and how to integrate into a multi-boot environment? Edit: Thought I'd mention that the Recovery CD's appear to be Windows PE so used the BartPE integration method which is also used with ERD Commander 2005... Also a STARTROM.COM file too.... I took a closer look at the boot sectors on this CD and the old one and I just noticed the new one references AMD64 on it, though the CD clearly has no AMD64 directory on it, and upon closer inspection of the actual setupldr.bin I notice many AMD64 references in there too, but again there's no AMD64 directory on the CD... ? Edit2: I replaced the setupldr.bin and stuff with the older ones from 2005, it goes through the loading, but at the end of the loading it says "Insufficient memory for CDFS.SYS" and stops....

I insatll Windows Defender and Ad-Aware on machines and tell people that Windows Defender will actively scan things, and Ad-Aware is for manual scanning in case they think Defender missed something.... I figure Ad-Aware is perfect to compliment Defender because it's not real-time protection, you actually NEED to start it to run it....

Thanks for this update Bash, I'm updating my DVDs now... I pretty much do my updates in tandem with yours since yours are the ones that resolve alot of my issues....

This post is just so people don't look at this as a seperate problem... I created a thread on this as well, though mine was related to the Biostar boards... http://www.msfn.org/board/index.php?showtopic=64949 Anyways, I basically discovered that the VIASRAID.* files are no longer necessary, like Muiz was saying they're just not used anymore and infact CAUSE the BSODs, simple rumage through the .CMD's and remove the entries (This is what I did to ensure I was right) or wait until Bashrat releases the newer mass storage pack....