Jump to content

meowing

Member
  • Posts

    135
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Posts posted by meowing

  1. wow, amazing and very interesting thing, maybe i'll try it on my xp sp3 x86 unattended installation, or like you said, I'll just wait for them to change their setup packages again ^^

    Unfortunately, I don't think nV is much aware of the issue. Their new beta driverpack (186.08) has the exact same problem when integrating for XP x64 Edition.

    Not only does it ruin unattended installs (it causes a Found new hardware dialog), it also fails to install properly right after setup/install of the OS has finished, because it seems to look for some .exe it can't find.

  2. I rename the .exe to .zip with TotalCommander and then unpack the content to a folder. No modifications or anything special.

    Just tested it;

    The 182.50 version works just fine, it's really wrong since 185.85. Nothing else is different in my nLite preset. Don't know what nVidia has done, but nLite doesn't like it! At least not on the GT 9600 hardware I test it on.

  3. I've been creating XP x64 Edition images ever since this was possible. I always add the latest nVidia drivers, and since they started creating the forceware packs this had become easy: Just grab the one .exe from here, unpack the exe, and let nLite find it as a Multiple driver folder and add it to the image that way.

    Always worked like a charm, until this latest version (185.85) when I noticed nVidia had cut down the amount of files in the setup folder by half (almost) and I have no idea how they managed to do so but they did. Ever since this has been done,

    the unattended installer gives a "Found new hardware" dialog during the stage where nLite.cmd is loaded, i.e. at the point where nLite's "Unattended settings" RunOnce commands are executed.

    After ignoring this dialog during setup (treating it as if it was still unattendable), it turns out not to have installed any nVidia driver at all when XP64 install has finished. All the other drivers did install as per usual.

    Anyone any idea how to solve this? Did something change within nvidia's setup.iss file that I do not know about?

  4. By the way, I use this in WINNT.SIF:

    [SetupData]
    OSLoadOptionsVar="/noguiboot /sos /noexecute=alwaysoff"

    which has the advantage of making the booting even faster than the other options. It will not load graphics at all, and jump straight through to (verbose echo) loading of the files.

  5. %Source%AddOns\Shockwave_Installer_Full.exe /S

    I'd use

    %Source%AddOns\sw_lic_full_installer.exe /S

    instead. The Shockwave installer you mention bothers you with sh_t about toolbars and norton and stuff.

    You can get the executable here

    And I can also recommend:

    %Source%AddOns\wmpfirefoxplugin.exe /Q /C:"msiexec /I ffplugin.msi /quiet /passive"

    ;-)

    You can get the executable here

  6. Jeroen Kessels is king for me. JKdefrag runs at true 64 bit (in Win XP x64) and is ideal for large disks with large files. It is much faster, smarter and more thoughtful than the others. I've been using it since 2002 and the others pale in comparison.

    I don't need a fancy interface, and I personally trust Jeroen. His forum speaks a thousand words of pure wisdom regarding Windows and harddisk usage. Last but not least, it's not so tough on SSD either.

  7. Kurt,

    rem Java runtime enviroment

    %Source%AddOns\jre-6u13-windows-i586-p.exe ADDLOCAL=ALL IEXPLORER=1 MOZILLA=1 /Passive /NoRestart

    %Source%AddOns\jre-6u13-windows-x64-p.exe ADDLOCAL=ALL IEXPLORER=1 MOZILLA=1 /Passive /NoRestart

    Where did you get the "jre-6u13-windows-i586-p.exe" file?

    I only see "jre-6u13-windows-i586-p-s.exe" being offered by Sun...

    Any idea what's with the added -s ?

  8. VMware runs XP x32 faster on my box than I've ever seen it run on a physical machine. That is if you've got at least 4 Gigs of ram so that neither the host or guest go thirsty. :)
    Just out of curiosity; Which type or version of XP (32 bit) do you run in VM? Just the stock release you have, or some of the famous nLited ones out there?

    I very much want VM inside my XP x64 to run a really stripped XP 32 bit (no browser, no Outlook, etc.) to be able to use it for that odd driver I can't run in XP64.

  9. Is meowing's sample size large enough to make such claims?

    Yes. Ever since my decision to not put them vertical anymore, I've had a clear decrease in HDD problems, both in my personal life and at work.

    Besides, *all* harddisks are still built on the exact same principles as the first ones that failed on me. There's not much difference between the oldest hard disk drive's structure and the newest. What was most stressing for them in the old days, is still the most stressing for them today.

    Gravity will pull the pick-up-needle to one side of the drive when you put it vertical. This will *always* wear out a drive's surface as well as put extra pressure on the engine that drives the needle (that makes it move over the surface of the platters). If you don't understand that, like I wrote, look at an old vinyl record player. HDDs are built very similar to that.

    http://www.youtube.com/profile?user=SuperF...deos&sort=v

  10. In my 29+ years of using harddisk storage media and recovering data from 'broken' disks, it is a clear-cut case for me that harddisks last longer when positioned horizontally. Of course manufacturers will state this isn't the case, but that's only because when they say it doesn't matter the HDs will wear out sooner so they simply sell more disks.

    I've worked at a broadcasting facility where all the seagates that were positioned vertically were full of bad blocks and ended their lives in about 4 years of non-stop 24/7 running in servers, while the exact same disks in the exact same types of servers which had the disks mounted the old way (flat, horizontally) lasted way longer and had significantly less bad blocks on them. I built, maintained and administrated those servers, so I know this is true and way too obvious to be mistaken. Ever since the year 2000 (when those vertical disks started dying on me), I stopped believing it doesn't make a difference.

    This is just my true life experience that caused me to never mount them in a vertical position again.

    I don't care what anyone says, it's quite logical too if you know what the insides of a HDD look like. You would never put a vinyl record player on its side. The wear and tear would be the wrong way.

    If you want your disks to live the longest, mount them horizontally, with the text-label side upwards.

  11. Be careful when downgrading too ... I downgraded a laptop from Vista to X64 and none of the important hardware works like my soundcard and wifi ... and finding drivers for those has resulted in a paperweight. The laptop never came with a Vista disc so I can't go back, and until I find the right drivers my laptop is useless.

    Did you ever try to use the Vista x64 drivers for your XP64, by installing/loading them manually. I now have sound on it as well, which was the hardest and last of the drivers.

    Practically ALL drivers for XP x64 were simply being offered by Intel and Nvidia and the likes, you just need to search their websites.

  12. meowing

    please try install all update pack and addons with nlite in one row.

    Made no difference. It seems that either

    - your slipstreamer does not create the required DirectShow registry keys for Win XP x64, or

    - K-Lite does not understand that vidc.M263 points to the SysWow64 folder, not the system32 folder (among many other mistakes).

    I'm blaming K-lite, since they target their codec pack at the 32bit crowd.

    Even though they offer their x64 pack as well, it doesn't solve this problem.

  13. Boooggy, sir,

    First of all, thanks for this great tool!

    I tried integrating WMP 11 into a clean legit XP x64 Edition SP2, after I used 5eraph's updatepack with IE6 updates using RVMi, adding DirectX addon (x86 + x64) as well, and then nLited the result without removing anything related to Windows Media (as far as I know..), but it seems WMA and WMV are entirely broken! I see errors related to WMedia and DirectSound when I install the KLite codec-pack.

    Have you ever tested an XP64 image (that has WMP11 + all hotfixes integrated using your tool) by installing Klite codec pack afterwards? I urge you to do so.

    I can't even play a wmv file, or watch an mms stream online. And I don't think it has to do with tweaks or removals from nLite. In case you wondered; Last Session.ini:

    Target = Windows XP Professional x64 Edition SP2

    [Tasks]
    Remove Components
    Unattended Setup
    Integrate Drivers
    Tweaks
    Create a Bootable ISO
    Options

    [Components]
    ;# Applications #
    Accessibility Options
    Briefcase
    ClipBook Viewer
    Defragmenter
    Games
    Internet Games
    Pinball
    WordPad
    ;# Drivers #
    ISDN
    Modems
    ;# Hardware Support #
    Brother Devices
    ;# Multimedia #
    AOL ART Image Format Support
    Images and Backgrounds
    Luna desktop theme
    Music Samples
    Old CDPlayer and Sound Recorder
    Speech Support
    ;# Network #
    Communication tools
    Connection Manager
    H323 MSP
    Internet Information Services (IIS)
    MSN Explorer
    Netmeeting
    Outlook Express
    Peer-to-Peer
    Windows Messenger
    ;# Operating System Options #
    Administrative Templates
    Color Schemes
    Command-line tools
    Disk and Profile Quota
    Document Templates
    DR Watson
    File and Settings Wizard
    File System Encryption
    Help and Support
    IExpress Wizard
    Manual Install and Upgrade
    MS Agent
    Out of Box Experience (OOBE)
    Private Character Editor
    Search Assistant
    Security Center
    Service Pack Messages
    Tour
    User account pictures
    ;# Services #
    Alerter
    Fax Service
    IMAPI CD-Burning COM Service
    Messenger
    Remote Registry
    Simple TCP/IP Services
    System Restore Service
    Telnet
    ;# Compatibility #
    Compat01
    Compat02
    Compat04
    Compat06
    Compat07
    Compat09
    Compat14

  14. What is the advantage of using Mkisofs instead of the Default in the Advanced - ISO Engine option for your Bootable ISO in nLite ?

    If your target is an XP x64 Edition bootable iso, which is your best bet and why?

  15. So, if the registry isn't yet fully built up at cmdlines.txt execution stage, it is probably best and safest to only put

    CMD /R some.bat

    in cmdlines.txt, and then put this in some.bat:

    REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\010 /VE /D "Building and Cleaning" /f

    REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\010 /V 1 /D "%WinDir%\ending.cmd" /f

    and put all the rest, including accessing the source image, in that ending.cmd, which can delete itself at the end of its own execution, when you put these in at the end of it;

    ATTRIB -R -A -S -H %WinDir%\ending.cmd >NUL

    DEL /F /Q %WinDir%\ending.cmd >NUL

    I've always really liked the idea of batch-files killing themselves ;-)

    By the way, I find that using a ping delay is more graceful than using timeout. Timeout echoes to the user, ping doesn't. I often use

    PING 1.1.1.1 -n 1 -w 1 >NUL

    where -n is the multiplier of -w in milliseconds. So

    PING 1.1.1.1 -n 4 -w 5000 >NUL

    delays the batch for ( 4 x 5000 ms =) 20 seconds.

  16. Oh yes, SSD will be mainstream real soon. I use an Intel X25 E as my main system's boot-drive, and it kills everything that dare called itself a storage medium. Somehow I feel a lot safer as well. Those old-school bad blocks are ridiculous.

    Also, check this and look at the price-drops for these:

    http://tweakers.net/ext/i/?ProduktID=223957

    http://tweakers.net/ext/i/?ProduktID=224949

    I assure you, its price-drop has begun, and it will not end anytime soon.

    If you want to throw (or, more provocatively, waste) large amounts of money on your storage devices then a pair of Seagate Cheetah 15K.6 HDDs run as a RAID 0 array driven by an Adaptec 5445 SAS RAID controller blew everything out of the water
    LOL, you seem to conveniently forget its noisy, vibrating, fragile, sensitive, hot and power-hungry aspects?
  17. Kurt, since you make a lot of use of the %SOURCE% variable in your scripts, I'd like to ask you this;

    Something's off with the %SOURCE% variable using my install image (from a XP x64 SP2 source). It doesn't seem to yield the right path during cmdlines.

    Here's my cmdlines content:

    [Commands]
    "rundll32 advpack.dll,LaunchINFSection nLite.inf,U"
    "runonce.cmd"

    (I have no nlite.cmd since I don't use/have anything under GuiRunOnce in WINNT.SIF)

    The "runonce.cmd" is in $OEM$, alongside cmdlines.txt, and I copied the way nuhi obtains his CD/DVD-drive letter, so my runonce.cmd looks like this:

    @echo off
    cmdow @ /hid
    for /f "tokens=3" %%i IN ('reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup /v "SourcePath" ^| findstr "REG_SZ"') do set SOURCE=%%i
    REG IMPORT %SOURCE%$OEM$\$$\2009.REG

    SET RDR=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx
    REG ADD %RDR% /V TITLE /D "Installing Software" /f
    REG ADD %RDR%\001 /VE /D "Last Minutes.." /f
    REG ADD %RDR%\001 /V 1 /D "%SOURCE%$OEM$\msxml6-KB954459-enu-amd64.exe /passive /qn /norestart" /f

    REG ADD %RDR%\005 /VE /D "Installing ERUNT" /f
    REG ADD %RDR%\005 /V 1 /D "%SOURCE%$OEM$\erunt-setup.exe /verysilent" /f

    REG ADD %RDR%\010 /VE /D "Inserting PSPad" /f
    REG ADD %RDR%\010 /V 1 /D "%SOURCE%$OEM$\pspad453inst_en.exe /VERYSILENT /SUPPRESSMSGBOXES /TASK=\"multiuser,txt\"" /f

    REG ADD %RDR%\030 /VE /D "Cleaning Up" /f
    REG ADD %RDR%\030 /V 1 /D "%WinDir%\ending.cmd" /f

    REG ADD %RDR%\035 /V 1 /D "COPY %SOURCE%$OEM$\PSPad.INI \"%ProgramFiles(x86)%\PSPad editor\\" /Y /Z" /f
    REG ADD %RDR%\036 /V 1 /D "COPY %SOURCE%$OEM$\PSPad_MU.ini \"%ProgramFiles(x86)%\PSPad editor\\" /Y /Z" /f
    EXIT

    This is just some example code. It ends up adding nothing in the place of %SOURCE% in the RunOnceEx reg-key, and this is really weird.

    The strange thing is that running ending.cmd (as it then is one of the RunOnceEx entries in reg) *does* yield the correct source of the install, using;

    FOR %%I IN (D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%I:\WIN51AP.SP2 (SET SOURCE=%%I:& GOTO DONECD)
    :DONECD

    which is in the top of ending.cmd...

    So when I move all the installers etc. from runonce.cmd to ending.cmd as a simple batch-file, they will work just fine!

    Any idea what I'm missing here?

    I haven't tried using

    SetLocal enableextensions
    SET CDISO=%~d0

    EndLocal

    in runonce.cmd yet, maybe that'll work..

×
×
  • Create New...