Jump to content

Sanjay

Member
  • Posts

    300
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    India

Everything posted by Sanjay

  1. Actually that is not correct. The Deluxe version has an entirely different and new nvidia chipset, 'nForce4 SLI x16' which also requires an entirely new and different driver. In fact nVidia has an entirely different driver set for this chipset.
  2. Any update on when you might get around to doing this? Thanks
  3. I have now tried this with making only a single user in 'oobeinfo.ini' and without the autologon.reg, but still no success. Even the single user is not being created and only the default windows 'Admistrator' account is being created. I can't believe that no one here on msfn can help with this. After all I am sure I am not the only one or the first one trying to have a complete Unattended Windows CD.
  4. =========== PCI devices =========== 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_10DE&DEV_0050&SUBSYS_00000000&REV_A4\3&267A616A&0&50: PCI standard ISA bridge PCI\VEN_10DE&DEV_0052&SUBSYS_CB8410DE&REV_A2\3&267A616A&0&51: NVIDIA nForce PCI System Management PCI\VEN_10DE&DEV_0053&SUBSYS_72201462&REV_F3\3&267A616A&0&78: NVIDIA nForce4 Parallel ATA Controller PCI\VEN_10DE&DEV_0054&SUBSYS_72201462&REV_F3\3&267A616A&0&80: NVIDIA nForce4 Serial ATA Controller PCI\VEN_10DE&DEV_0055&SUBSYS_72201462&REV_F3\3&267A616A&0&88: NVIDIA nForce4 Serial ATA Controller PCI\VEN_10DE&DEV_0057&SUBSYS_72201462&REV_A3\3&267A616A&0&98: NVIDIA Network Bus Enumerator PCI\VEN_10DE&DEV_005A&SUBSYS_72201462&REV_A2\3&267A616A&0&58: Standard OpenHCD USB Host Controller PCI\VEN_10DE&DEV_005B&SUBSYS_CB8410DE&REV_A4\3&267A616A&0&59: Standard Enhanced PCI to USB Host Controller PCI\VEN_10DE&DEV_005C&SUBSYS_00000000&REV_A2\3&267A616A&0&90: PCI standard PCI-to-PCI bridge PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&267A616A&0&A0: nForce4 PCI-Express Root Port PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&267A616A&0&B0: nForce4 PCI-Express Root Port PCI\VEN_10DE&DEV_005D&SUBSYS_00000000&REV_A3\3&267A616A&0&B8: nForce4 PCI-Express Root Port PCI\VEN_10DE&DEV_005E&SUBSYS_72201462&REV_A4\3&267A616A&0&48: nForce4 HyperTransport Bridge PCI\VEN_10DE&DEV_0161&SUBSYS_81BA1043&REV_A1\4&A70D623&0&0020: NVIDIA GeForce 6200 TurboCache(TM) PCI\VEN_10DE&DEV_027E&SUBSYS_72201462&REV_A2\3&267A616A&0&07: nForce Memory Controller PCI\VEN_10DE&DEV_027F&SUBSYS_72201462&REV_A2\3&267A616A&0&06: nForce Memory Controller PCI\VEN_10DE&DEV_02F4&SUBSYS_72201462&REV_A2\3&267A616A&0&00: PCI standard RAM Controller PCI\VEN_10DE&DEV_02F8&SUBSYS_72201462&REV_A2\3&267A616A&0&03: nForce Memory Controller PCI\VEN_10DE&DEV_02F9&SUBSYS_72201462&REV_A2\3&267A616A&0&04: nForce Memory Controller PCI\VEN_10DE&DEV_02FA&SUBSYS_72201462&REV_A2\3&267A616A&0&01: nForce HyperTransport Bridge PCI\VEN_10DE&DEV_02FB&SUBSYS_00000000&REV_A1\3&267A616A&0&20: PCI standard PCI-to-PCI bridge PCI\VEN_10DE&DEV_02FC&SUBSYS_00000000&REV_A1\3&267A616A&0&10: PCI standard PCI-to-PCI bridge PCI\VEN_10DE&DEV_02FD&SUBSYS_00000000&REV_A1\3&267A616A&0&18: PCI standard PCI-to-PCI bridge PCI\VEN_10DE&DEV_02FE&SUBSYS_72201462&REV_A2\3&267A616A&0&02: nForce Memory Controller PCI\VEN_10DE&DEV_02FF&SUBSYS_72201462&REV_A2\3&267A616A&0&05: nForce Memory Controller PCI\VEN_1102&DEV_0007&SUBSYS_10091462&REV_00\4&2411F011&0&2890: Sound Blaster Audigy PCI\VEN_1106&DEV_3044&SUBSYS_220D1462&REV_46\4&2411F011&0&2090: VIA OHCI Compliant IEEE 1394 Host Controller PCI\VEN_11AB&DEV_4362&SUBSYS_058C1462&REV_15\4&23E04D34&0&0018: Marvell Yukon 88E8053 PCI-E Gigabit Ethernet Controller PCI\VEN_12B9&DEV_1006&SUBSYS_006812B9&REV_00\4&2411F011&0&3890: U.S. Robotics 56K Voice Win 1806 33 matching device(s) found. =========== USB devices =========== USB\ROOT_HUB\4&9888FC4&0 : USB Root Hub USB\ROOT_HUB20\4&16C75017&0 : USB Root Hub USB\VID_03F0&PID_1204\MY01H11141JJ : USB Printing Support USB\VID_0733&PID_0430\5&E127332&0&3 : Intel PC Camera Pro USBPRINT\HEWLETT-PACKARDDESKJET_930C\6&12BE9078&0&USB001 : HP DeskJet 930C/932C/935C 5 matching device(s) found. This is what I get as a result of running 'save_hwids.cmd'. Please keep in mind, that I have installed the Drivers and Utilities from the bundles Creative installation CD'. I don't know if that makes any difference to the results above of the HWIDs. Basic sound does work from the Driver Pack installation, but the driver displays as ''Sound Blaster Live! 24, Creative v5.12.1.512 dated ' whereas after I ran the bundled Creative CD, the Driver displayed as 'Sound Blaster Audigy, Creative v5.12.1.519 date 21/10/2005'. Ofcourse no control panel was installed from the Driver Packs.
  5. Please note that I was busy editing my previous post when you posted, so please refer to my previous post again. Regarding my HWID's where and how do I look for those? The Driver Pack I used was BasePack 6.02.1 and all of the Driver Packs. I shall reuse this DVD to install again and I will make a note of and post here the exact error message in the blue screen, when and if I get it.
  6. @5eraph Thanks for the detailed explanation, the issue is a lot more clearer to me now. By the way I tried an installation with a complete Driver packs slipstreamed installation on the 'MSI K8N Diamond Plus (nForce4 SLI 16X)' and I got a blue screen upon first boot. I tried rebooting a couple of times but with the same result. I then Booted into safe mode and let the GUIRunOnce (start.cmd) finish with the installation. Ofcourse a lot of the programs in my 'start.cmd' did not install because of windows being in 'Safe' mode, but after finishing when the computer rebooted, it was able to do so without getting a blue screen. I wonder what this implies or means in terms of the long term stability of the OS installation. Also, the 'MSi K8N Diamond Plus' has the "Creative sound Blaster Audigy SE audio' built in, but the driver that got installed is the 'Sound Blaster Live! 24, Creative v5.12.1.512 dated ' instead of 'Sound Blaster Audigy, Creative v5.12.1.519 date 21/10/2005'. The second driver is what it shows when I installed from the included Creative CD. Also, none of the Creative utilities were installed. I have not yet tried this with the 'Asus A7N8X-E (nForce2 Ultra)' and quite honestly I am not inclined to do so also. For now I think I am going to stick to my own manual slipstreaming of drivers rather than Bashrat's Driver Packs, atleast until all this sorts itself out or I understand it better.
  7. Thanks for your response. But I don't think that this is the problem. THe reason I say this is that the Unattended CDs I have made in the past which work perfectly, also did not have any password assigned to the Users. Also since I don't have any password assigned it would be logical for there not to be any password in 'autologon.reg'. But having said this I will try this by assigning a password and see. At this point I am willing to try anything. Thanks again.
  8. I cannot for the life of me figure out what is causing a problem in my Unattended CD not being able to make any 'Users'. In the past I have been able to succesfully create multiple users with my Unattended CD. The only time I had problems was when I ran it in VMware, but otherwise in real installations I had no problems at all. But now I end up with the following error: I have compared the following 'oobeinfo.ini, autologon.reg, stopautologon.reg, Start.cmd' from my older working CD, with my current cd and can't find any difference at all. But for some reason it just won't work anymore.I have been using the following method: I have not made an Unattended CD for a long time and now that I have made one I can't get this to work. I end up with the following error message: The one major difference between my earlier working Unattended CDs and the current one is that I am now using the 'RVM_Integrator_1.0.5.exe' integrator to integrate RyanVMs Update pack and other addon packs. This is something I did not do in any of my older CDs. Could this be the problem? My Winnt.sif file has the following entries: ;SetupMgrTag [Data] AutoPartition = 0 MsDosInitiated = "0" UnattendedInstall = "Yes" AutomaticUpdates = Yes [Unattended] UnattendMode = FullUnattended UnattendSwitch = Yes OemSkipEula = Yes OemPreinstall = Yes Hibernation = Yes TargetPath = \WINDOWS DriverSigningPolicy = Ignore OemPnPDriversPath = "Drivers\SATA\SiI3112r;Drivers\SATA\SiI3114r;etc\etc" [SystemFileProtection] SFCQuota = 0 [GuiUnattended] AdminPassword = "wxyz" EncryptedAdminPassword = NO OEMSkipRegional = 1 OEMSkipWelcome = 1 TimeZone = 190 [UserData] ProductKey = xxxx-xxxx-xxxx-xxxx-xxxx FullName = "J. Doe" OrgName = "Semtech XYZ Inc." ComputerName = Semtech [Branding] BrandIEUsingUnattended = Yes [Proxy] Proxy_Enable = 0 Use_Same_Proxy = 1 [Identification] JoinWorkgroup = WORKGROUP [Networking] InstallDefaultComponents = Yes [GuiRunOnce] Command0 = %systemdrive%\install\start.cmd Could any of these be the problem?: 1. Having set a password for AdminPassword? --> [GuiUnattended] --> AdminPassword = "wxyz" 2. Or could this be the problem? The Error message did say something about a correct user name and domain. --> [identification] --> JoinWorkgroup = WORKGROUP 3. Or could something in RyanVMs update pack and/or the other addon packs be causing the problem? Because that is the one major change from my earlier working Unattended CDs. I really need to get this working, any and all help will be greatly appreciated. Thanks.
  9. Does it mean that a common Unattended CD using the DriverPacks will be able to install the correct 'nForce4 SLI 16X' drivers and utilities for the 'MSI K8N Diamond Plus' and also the correct 'nForce2 Ultra' drivers and any utilities for the Asus A7N8X-E. Or should I simply make a seperate CD for each, but obviously in that case I would not be able to use the Chipset Driver pack? Please excuse my questions if they seem repetitive. But since reading of the problems caused by multiple nForce drivers present in an Unattended CD, I am looking for an answer that would clearly tell me what exactly is the problem that is caused.
  10. Based on some of the threads I have read here it seems that the existence of mutiple nForce drivers for various new nVidia chipsets is causing a lot of problems. Although I have gotten the gist of the problem I am not sure I understand the ramifications of it completely. Other than the basic problem of having to keep up with mutiple versions of the nForce drivers, an explantion as to what exact problems this situation creates would be appreciated. More importantly I am concerned about how this effects my Unattended CD and the DriverPacks. I have two PCs. 1st PC: Motherboard - MSI K8N Diamond Plus Chipset: nForce4 SLI x16 Driver: nForce4 AMD-Intel X16 - Windows XP2000 (32-Bit) v6.85 2nd PC: Motherboard: Asus A7N8X- E Deluxe Chipset: nForce2 Ultra Driver: nVidia nForce Windows XP - Unified Driver Package 5.10 Does it now mean that I cannot make a common Unattended CD for both systems by having both drivers present? What about an Unattended CD with Bashrat's Chipset DriverPack, I assume it has both drivers built in, will that work for both motherboards or not? What exactly will happen if I were to use the Unattended CD with both drivers present to install on my two PCs? Thanks.
  11. Thanks a lot. I will eagerly await the msi installer for v9.
  12. There is a new driver for the 3112 Sata Raid controller which is dated 11/10/2005. The 'Silicon Image Serial ATA RAID driver for SiI3x12r' has been updated after a very long time and is now at version 1.0.0.53. Would like to rquest the MassStorage pack be updated with these drivers. Thanks.
  13. I would like to second this request. This new 'SiI3132 32-bit Windows SATARAID5 Driver 1.3.0.9' supports RAID levels 0, 1, 5, and 10.
  14. LEt me be the one to 'Third' this request.
  15. Thanks for the response. Eagerly waiting for the updated Chipset, Graphics & Mass Storage Driver Packs.
  16. I think it works fine in VMware when you have only a single user but not if you have multiple users. I am just guessing here and am not very sure about this. The real reason I revived this thread is that I have run into some User login issues, but then after posting in this thread i realized there is a more appropriate thread --> Link to thread to post in.
  17. Thanks for the reply. Although your instructions on how to go about using the v8 msi for v9 are still quite unclear to me. But thanks anyhow.
  18. How do you open the Easy CD-DA Extractor 8.2.1 Build 1 .MSI Installer?
  19. A new raid driver for Silicon Image 3132 has been out since November 28, 2005. The new driver is 'SiI 3132 32-bit Windows SATARAID5 Driver version 1.3.0.9'. Any idea when this will be incorporated into 'Driverpack MassStorage', basically when will Driverpack MassStorage be updated from v5.10? Thanks.
  20. Does this have support for the nForce4 SLI X16 chipset? Also there is a new nForce4 SLI X16 chipset driver v 6.85 released 2/2/06.
  21. How does one silently install v8.2.4.1? How does one make an MSI installer for the new Easy CD-DA Creator v8.2.4 Build 1?
  22. How does one make an MSI installer for the new Easy CD-DA Creator v8.2.2 Build 1?
  23. Actually 'wpdsp.dl_' is also already present in wmp.cab from ryan's wmp pack.
  24. This is what you get when you try to open Yahoo mail. Yahoo! may not be optimized for the web browser you are using. Your options are: Upgrade to Internet Explorer 6.0, Netscape 7.1, or Safari 1.2. Switch back to the Yahoo! version supported by your current browser. If you click on 'Switch Back to Yahoo version supported......' you are able to access your Yahoo email.
×
×
  • Create New...