Jump to content

Sanjay

Member
  • Posts

    300
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    India

Posts posted by Sanjay

  1. @Sanjay

    The driver will work as long as you don't use the tool sysprep.

    sysprep is a tool for pc manufactures to ship the pc to the end user.

    kyor

    Thanks for the info. But it does work with an unattended install atleast it does in my case, which means it should not affect most people since we don't use sysprep anyhow.

  2. I think I have figured out what the confusion is. It is limited to the two files that are changed by both myself and nLite, namely the files being, txtsetup.sif and dosnet.inf When I stated that upon using nLite before adding my stuff I forgot to mention that I also replaced txtsetup.sif and dosnet.inf with my versions which obviously did not inlude the changes by nLite and thus the errors with the installation. On the other hand when I first added my files and then used nLite everything went smoothly although this time I installed on a computer with no SATA drives so therefore for all I know that might not be working as per what RyanVM has experienced. Although I must say that upon checking the file itself I still see the entries that I made to txtsetup.sif regarding SATA, very much present.

  3. EDIT: But yes, RUN NLITE BEFORE MAKING ANY OTHER CHANGES TO THE CD.

    What RyanVM said ;)

    Sorry, but I think you guys are wrong. Why do I say so? Well for starters as mentioned above my experience shows that it is the other way around. Also I think it has to do with the fact that nLite makes changes to certain files and specially to textsetup.sif so if I were to make changes to the CD after nLite that would mean replacing the 'textsetup.sif' file also, since slipstreaming of SATA drivers requires changes to the 'textsetup.sif' file. I guess what you guys might be suggesting is that I use nLite first on a fresh Windows and then make my changes to the 'Textsetup.sif' file fromt he nLite package, rather than replacing it, right?

  4. Note that the Marvell drivers currently don't work in unattended setups. This only occurs when you use Service Pack 2. Let's hope they update their drivers soon...

    Bâshrat the Sneaky

    Strange, but they seem to work just fine with my unattended CD and yes it is with slipstreamed Service Pack 2.

    By the way the Driver I am using is:

    DriverVer=09/22/2004, 7.23.1.3

  5. EDIT: But yes, RUN NLITE BEFORE MAKING ANY OTHER CHANGES TO THE CD.

    Strange, the first time I used nLIte on a fresh Windows CD to reduce it's size and then added my stuff which gave me all the missing file errors. But the second time I first added all my stuff to a fresh Windows CD and then used nLite to reduce the size, this time total success.

    Thus can someone please tell me which is the right way.

  6. using this in batch file

    ECHO installing Nero 63117

    start/wait %systemdrive%\Install\nero63117.exe /SILENT /NOREBOOT /****KEY****/WRITE_SN

    still need to enter key after install any ideas please.

    STW

    You probably need to add 'SN=' before the actual KEY.

    ECHO installing Nero 63117
    start/wait %systemdrive%\Install\nero63117.exe /SILENT /NOREBOOT /SN=****KEY****/WRITE_SN

  7. @Sanjay:

    Edit your post, there are something contradictory

    'Windows Media Connect' works perfectly. [cut] 'wmcsetup7.exe' it just starts with the extracting process, and then nothing...
    or off-topic:
    your similar method for 'Media Player 10', does not work

    Sorry about that, post now edited. It should have been 'mp10setup7.exe'.

  8. This is what I have added to my textsetup.sif based on what is suggested by SI3114R.OEM file of 'xpcreate.cab':

    [SourceDisksFiles]
    si3114r.sys = 1,,,,,,4_,4,1,,,1,4

    [HardwareIdsDatabase]
    PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "si3114r"
    PCI\VEN_1095&DEV_3114&SUBSYS_288510F1 = "si3114r"
    PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0 = "si3114r"
    PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0 = "si3114r"
    PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0 = "si3114r"
    PCI\VEN_1095&DEV_3114&SUBSYS_90181695 = "si3114r"
    PCI\VEN_1095&DEV_3114&SUBSYS_F642270F = "si3114r"
    PCI\VEN_1095&DEV_3114&SUBSYS_100415BD = "si3114r"

    [SCSI.load]
    si3114r = si3114r.sys,4

    [SCSI]
    si3114r = "Silicon Image SiI 3114 SATARaid Controller"

    This is in addition to what I had already entered for the SiI3112r as above. I hope this is correct. I cannot test the CD right now so if I have made any mistakes please let me know.

    Thanks,

    Sanjay

  9. I am further confused now. Although my unattend CD has been working fine so far I just noticed that the lines that I added to my Textsetup.sif are different from what have been mentioned in the SI3112R.OEM file of 'xpcreate.cab'

    This is what is suggested should be in the Textsetup.inf as per SI3112R.OEM from xpcreate.cab

    [SourceDisksFiles]
    si3112r.sys = 1,,,,,,4_,4,1,,,1,4

    [HardwareIdsDatabase]
    PCI\VEN_1095&DEV_3112&SUBSYS_61121095 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_611215D9 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_34228086 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_B0031458 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A0111019 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A0121019 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A0131019 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A0141019 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A0151019 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_1014147B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_100B147B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_1402147B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_1404147B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_1802147B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_1804147B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_1C00147B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_5930107D = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_249510F1 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_809D1043 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0270A0A0 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_044DA0A0 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_044CA0A0 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_92011905 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_92151905 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_904C1905 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_904B1905 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A41810FD = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A41910FD = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_A71910FD = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_90171695 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_C2001297 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_C2011297 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_15D40035 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_340217F2 = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_100415BD = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_F641270F = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C0F105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C13105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C58105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C40105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C41105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C42105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C43105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C44105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C22105B = "si3112r"
    PCI\VEN_1095&DEV_3112&SUBSYS_0C2A105B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_65121095 = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_B0031458 = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1014147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1021147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_100B147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1C06147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1C00147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1C03147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1C04147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1406147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_1407147B = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_90191695 = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_C2021297 = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_C2031297 = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_C2041297 = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_534D108E = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_02B71014 = "si3112r"
    PCI\VEN_1095&DEV_3512&SUBSYS_02C51095 = "si3112r"
    PCI\VEN_1002&DEV_436E&SUBSYS_436E1002 = "si3112r"

    [SCSI.load]
    si3112r = si3112r.sys,4

    [SCSI]
    si3112r  = "Silicon Image SiI 3112 SATARaid Controller"

    This is what I have in my Textsetup.inf file:

    [SourceDisksFiles]
    si3112r.sys  = 1,,,,,,_x,4,1

    [HardwareIdsDatabase]
    PCI\VEN_1095&DEV_3112&SUBSYS_61121095 = "Si3112r"

    [SCSI.load]
    si3112r = si3112r.sys,4

    [SCSI]
    si3112r = "Silicon Image SiI 3112 SATARaid Controller"

    Howcome everything seems to be working fine on my CD, even though my entry under [sourceDisksFiles] is different and I only have a One line entry under [HardwareIdsDatabase] instead of the Sixty Six lines as per SI3112R.OEM from xpcreate.cab

  10. Thanks but those instructions are for SiI3112r, what do I do in the case f SiI3114r? I figured I could simply just use 'SiI3114' instead of 'SiI3112r', but the problem is that all the files in the two drivers are not the same.

    The files in the SiI3112r driver are:

    si3112r.cat

    Si3112r.inf

    Si3112r.sys

    SiiSupp.vxd

    SilSupp.cpl

    SIWinAcc.sys

    TxtSetup.oem

    The files in the SiI3114r driver are:

    si3112r.cat

    Si3112r.inf

    Si3114r.mpd

    Si3112r.sys

    SiiSupp.vxd

    SIWinAcc.sys

    TxtSetup.oem

    The two files in BOLD are different from each other, so what do I do?

    Thanks,

    Sanjay

  11. I have two computers with the following motherboards.

    1. Asus A7N8X-E Deluxe with bundled WLAN card (Silicon Image SiI3x12)

    2. Asus K8N-E Deluxe (Silicon Image SiI3x14)

    I already have the 'Silicon Image Serial ATA RAID driver for SiI3x12r version 1.0.0.51' slipstreamed and working fine for the first system.

    I would now like to add the 'Silicon Image Serial ATA RAID driver for SiI3114r version 1.0.0.7' also, so that I can use a common Windows unattended CD for both systems.

    Is it possible to do this and is it advisable? If it is possible and there is no negative side to ti, then how do I do it?

    Thanks,

    Sanjay

  12. Just as the title suggests, I would like to be able to make/copy some shortcuts in/to the 'Quick Launch' toolbar. I have already tried the '$OEM$\$DOCS\{USER}\Application Data\Microsoft\Internet Explorer\Quick Launch' method but it does not work. The files do get copied over to the particualar {USER} Documents and Settings folder but the problem is now Windows does nto use that name for the USER. Instead it makes a User by the name {USER-COMPUTER NAME}

    For eg.:

    Let's say I have a user by the name of Sanjay and my Computer Name = 'Visualtech', thus:

    '$OEM$\$DOCS\Sanjay\Application Data\Microsoft\Internet Explorer\Quick Launch', which insures that the shortcuts get copied over to that path. But the problem is that windows now does not use the name Sanjay as a user and instead uses Sanjay-Visualtech as the name for the user.

    Anyhow I am hoping someone can help me solve this problem. I have 5 users that I would like to make and would like to be able to copy shortcuts to the Quick Launch toolbar of all five. Shortcuts to stuff like 'Calculator, Notepad, Windows Media Player 10' etc.

    Thanks.

  13. That's what his method for wmc did for me...just extracted 'somewhere' and stopped.

    Don't think the problem was btwn the keyboard and chair...unless Nilfred meant his keyboard and his chair...heh, heh.

    But it works fine for me for 'wmc', it is only with mp10 that it does not work.

    I wonder if it would be possible for someone to host working copies of 'mp10setup7.exe' and 'wmcsetup7.exe'. I am willing to upload my working copy of 'wmcsetup7.exe'. This will save a lot of people a lot of grief. Now that is a lot of lots. :)

  14. Well, tested unnatended on vmware works fine here :}

    It does not work for me at all. I have tried it in a real unattend install via 'svcpack' but nothing I just ended up with Media PLayer 9 installed. Funny thing is Windows Media Connect installed properly which also I had put in 'svcpack'. I thought Windows Media Connect required Media Player 10 to already be installed, strange.

    By the way I even tried just running the file in Windows and still no luck. For some reason when you run the 'wmcsetup7.exe' it just starts with the extracting process, and then nothing... it just dissapears. I have retried the whole process several times but with no luck. I then used the winrar.sfx method as suggested by 'GreenMachine' and it works perfectly. Only problem is the size of the file being about 4mb bigger. Since I really don't have the extra space on my CD it is kinda useless for me unless I sacrifice something else. Thus I would really like to be able to make Nilfred's method work. Any ideas, how?

  15. Nilfred's method for 'Windows Media Connect' works perfectly. It also works without giving any System Restore Message even if you have System Restore off.

    @Nilfred

    For some reason your similar method for 'Media Player 10', does not work. When you run the mp10setup7.exe' it just starts with the extracting process, and then nothing... it just dissapears. I have retried the whole process several times but with no luck.

  16. The final result is the same: the difference is in the tools used. Nilfred's  method does create a smaller file, so perhaps it is better.

    Thanks for the quick reply. Space is a big problem on my CD so I guess Nilfred's method is what I stick with.

  17. o.O

    thanks for pointing that out

    maybe that's why oobe didnt work for me

    but it never actually created the account, so that might be a totally different thing

    You are welcome and yes you are right that is why oobe did not work for you. All you have to do is use it on a real install and believe it works just fine. By the way you are right, when trying this in VMWare oobe fails to creat the users and that is why the error regarding not being able to find the user and logon.

  18. Did it place the icon in the Quick Launch bar immediately, or did you have to run the program first and then go through the setup?

    In my experience it does not place the Icon in Quick Launch Toolbar. It is only when you run the program and go thru the setup that it places the icon in the Quick Launch Toolbar. In my case since I use the foillowing registry tweaks:

    ;-----  Media Player Stuff
    ;-----
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsMediaPlayer]
    "GroupPrivacyAcceptance"=dword:00000001

    ;-----
    [HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences]
    "AcceptedPrivacyStatement"=dword:00000001
    "FirstRun"=dword:00000000
    ;-----

    ;-----  Enable DVD in Media Player
    ;-----  Value: Yes or No
    [HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Player\Settings]
    "EnableDVDUI"="Yes"
    ;-----

    ;-----  Set Windows Media Player MP3 Encoding Bitrates
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\Settings\MP3Encoding]
    "LowRate"=dword:0001f400
    "MediumRate"=dword:0002ee00
    "MediumHighRate"=dword:0003e800
    "HighRate"=dword:0004e200
    ;-----

    there is no setup process so I end up with no Icon in the Quick Launch Toolbar, although I would like it to be there.

×
×
  • Create New...