Jump to content

meowing

Member
  • Posts

    135
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Posts posted by meowing

  1. What's the best way to dual-boot two OS-installs of XP x64 Edition SP2, while using only one $OEM$ precopy folder?

    I'd also like to maintain the original CD folder structure of both OS-isos, because I require the official volume-name (at work) in tact,

    I just need the 2 choice dialog at boot, no fancy stuff, so cdshell looks like overkill to me.

    Tried employing the reanimato tool (http://bootcd.narod.ru/index_e.htm) but it errors out everytime it starts setup on each of the two.

    As I understand, I at least need to copy ntdetect.com and setupldr.bin from both the i386 folders one folder higher up, so they are in their respective install-root folders, but I have no clue how they need to be hexed. Let's say my iso-root folders are called \XP_1 and \XP_2 and I also have the \$OEM$ in the root of the dual-boot-installer; What is the best way to go about creating a dual-boot menu and switch for that?

  2. for /f "delims=: tokens=1" %%i in ("%~dp0") do set drive=%%i:
    set wpipath=%drive%\wpi

    SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

    REG ADD %KEY%\WPI /V 1 /D "%wpipath%\WPI.hta" /f

    Just a check to be sure; At what T- stage do you best run this via .cmd (for XP x64 Edition setup/installer) ?

  3. Good, very good news, from German-WinLite.de !

    In NV4_DISP.INF,

    under [DestinationDirs],

    just change that:

    nv_controlpanel_copyfiles = 01

    to that:

    nv_controlpanel_copyfiles = 11

    It's amazing but that's it. I've just tried it and it worked with the good old method of pointing the *.inf folder in the winnt.sif.

    So many thanks for beatmaster and his post http://german-winlite.de/wbb/index.php?pag...29267#post29267

    What does this do? I mean, you say something is good news, but it's not clear what is. Does this work for XP x64 as well?

  4. Meowing, I think I'll just leave it unsupported for now. I just don't feel comfortable with adding a direct link to a version that would normally require one to agree to a redistribution license.

    The link got emailed to me a long time ago by someone still using a Macromedia e-mail address. This was when I asked them about support for HomeSite as a separate software distribution. Homesite is now part of Dreamweaver. I think they maintain this direct-download for several older software packages (automatic downloads by those) and are licensed by Adobe to offer it that way. As a user you don't need to have a license before downloading, or they failed to tell me about it anyway..

    It is the most recent version, as I see here: http://www.adobe.com/shockwave/welcome/

  5. August updates

    4. Removed support (remarked out) for Adobe Shockwave, I swear that thing has a VM detector. It will install silently in VMware Server or VirtualBox but asks to install a toolbar when installing (using same image) on a real machine.

    As was stated by me a couple of months ago in this post:

    I'd use

    %Source%AddOns\sw_lic_full_installer.exe /S

    instead. The Shockwave installer you've commented out bothers you with sh_t about a toolbar and stuff.

    You can get the executable that does not do that here

  6. Yes I've seen many posts and threads about it, but not one true solution, which is why I posted this. Either you have to strip the pack clean of Physx and the controlpanel, or you end up changing inf files manually in ways that are obscure at best.

    I'd rather have the entire install as is, as it used to be.

  7. Ever since version 185.85 WHQL, we can no longer integrate the drivers from nVidia using nLite. The install stops with a Found New Hardware dialog, and it causes the nlite commands (thus entire installation of Windows) to not be executed properly any further.

    I tried editing NV4_DISP.INF, but that makes the drivers no longer WHQL, no longer certified, so you're pretty much stuck.

    I'm surprised there aren't many others posting about this, not even in the nVidia forums.

    Sincerely hoping someone with a bit more knowledge knows how to best solve this.

  8. I've tried integrating the last version (190.38) onto my unattended cd from winnt.sif and it still doesn't work, same install same problem.
    Same here. I've been trying this for weeks now. I don't see where the problem is. It is rather annoying that nvidia changed this.

    I don't think the problem is with nlite. Nor do I expect Dino to change things because of it.

    Why is NVidia doing this?

  9. XP has cleartype disabled by default, and 90% of people don't change from defaults, so it will be a new experience for people.

    I also used to think that Cleartype was bad, as I had a CRT, but it looks much better on a LCD. In my experience anyhow.

    I don't see how that's even possible. You probably don't use the native 1:1 resolution on your LCD, because I'm never bothered with sharpness of type. The harder the edges, the more legible the fonts are to me. Oh and yes, the color-noise it generates is awfully distracting too.
  10. good to know how it works.

    that "smooth" effect is what i don't like though.

    the "hard" lines are what i do like.

    and i can't notice any "jaggies" at 1920x1200.

    Same here. The smoothing is bulls*** to my eyes. Either cleartype never does it the way I would like it to, or I prefer hard lines over soft edges. Also, NOT being able to see where it goes wrong in fonts would be my preference over software regulated changes in displaying of them. My eyes can handle a jaggie here or there just fine, thank you very much. ;-)

    And no, it does not make a difference what screen I see it on. I have owned about 10 different ones, and my latest favorite screen is a NEC 26 inch LCD. My eyes always notice cleartype-effects as something distracting and unwanted. Will not change for me ever, either.

  11. yea, the tuner still does not help, the text is actually more clear with cleartype off, very odd.

    must just be me then.

    No, I'm with you all the way. I have never understood the use of cleartype. It makes my fonts blurry (whatever other people say about it, blurring *is* what happens, on every screentype), which I really detest strongly. I've created truetype fonts for a living for a couple of years in the nineties, so maybe that has something to do with it. I always like my fonts to be displayed as sharp and original as they possibly can be.

  12. Isn't the point of using the WMP11 Slipstreamer so that it slipstreams it into the source to begin with?
    Yes, and that is what happens when you place WMP11 installer into the nLite Hot Fix section. It is detected and nLite calls booogy's slipper.
    Is this method in any way preferred over simply using booogy's slipstreamer after having nlited a source image, and if so why? (I ask this because the added hotfixes belonging to WMP in booogy's tool are confusing me when I do it in the middle of having nlite busy with an image already.)
  13. Windows XP Professional x64 Edition (with the Windows 2000 look). Best OS ever. Incredibly stable and reliable. Brilliant memory management, VERY fast.

    Pretty sure I'll be using this next to Linux and ReactOS for a long d_mn time. To be perfectly honest, I don't understand the whole fancy-_ss 3D OS-stuff one iota. I never use all the cute screen things for anything, so I end up switching them off. I use my computers in a different way I guess; Not to show them off to people, not to make its screens look nice and flashy. I like purity, stability, reliability and speed. No useless time-wasting moving items on my screen that are in no way making it more productive for me.

×
×
  • Create New...