Jump to content

Oleg_II

Member
  • Posts

    679
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    China

Posts posted by Oleg_II

  1. Innocent Devil

    I personally had some problems with installing my HP printer. The drivers said 2003 is unsupported. I found a workaround by modding the .ini file in the drivers. You might have to do something like that in rare cases.
    Could you give an example of how to mod this, please :rolleyes:
  2. And unlike WIM and VMDK formats, Symantec hasn't taken too many steps towards publishing specs for theirs.
    Yes, it's proprietary code. But it's not bad because of that :rolleyes:

    Innocent Devil

    It is not about what you can do or can't. I replied to your "better then Ghost-like". 7zip is not Ghost-like but it also can do the job (I'm not discussing how, yes it will be more resource taking). If you are comparing with Ghost like, I can't agree - I use DeployCenter, can make highly compressed images in DOS and fomr PE, can restore disk with all partitions, restore separate partitions or individual files and folders with ease and with more comfort then with WIM. WIM is not better then Ghost-like :whistle:

  3. dexter.inside

    I'm not saying that WIM technology is bad. But it's not easy and comfordable at the moment (and when it will be, if ever, there will be more alternatives ;) I just showed how it could be replaced with known appz.

    You can't mount a 4 Gb 7z archive as a NTFS junction and service it offline.
    Use image browser to open image. And using latest version of PowerQuest products - Symantec Backup Exec System Recovery for example, not sure but with Image Explorer from Ghost v12 should work the same way - you can mount images as virtual hard drives and serve them as you wish :)

    You can use third party appz for moounting 7zip archive like a virtual disk (commercial app - Winmount, can even mount Ghost images by the way and uses very low resources). Sorry, I can't give you a freeware example as I'm not using this (using Ghost like imaging - DeployCenter).

    You have no integrity checking when capturing over network.
    Use Image Explorer to verify image integrity.
    2) WIM technology also allows easy diffing / differential packaging, suitable for Embedded purposes. A componentized XP / Vista will benefit the most from this type of packaging, due to the very efficient system of single instance storage.
    Make a 7zip archive with a few folders inside for each component.

    PS What I was pointing to: I'm not saying that using Ghost is better, but it is not right to say "it's completely different". For this purpose - imploying system - the implementation is nearly the same.

  4. Innocent Devil

    WIM is not like Ghost
    In this case it acts nearly the same way (I agree with some of your points but continue to read ;)
    while Ghost uses sector based imaging of the hd
    but for ghost it wipes out old files and u only have new files, it doest cares for files but to harddisk sectors it requested to copy
    Not exectly right. Agree as for part with wiping. Ghost has sector to sector copy function (using switches it copies even deleted from hard drive files into image for heavy recovery or forensic purposes) but it usually copies only files on disk and doesn't copy all sectors by default. It is implying file system structure and boot sector but it is not sector per sector copy ;)
    with wim u can apply the image to a non empty partition and at the end u have both old files in tha partition and the files from wim
    To appy wim image you have to load PE evironment, right? But if you add to your PE compilation some archivator, say freeware 7zip, you can use it to zip/unzip files to a non empty partition without damaging already existing files and folders :whistle:

    Wim VS 7zip :rolleyes:

  5. I think it is very helpful fo ppl installing XP for large num of s/ms
    Yes, that works :thumbup

    But... When you are deploying to computers with similar hardware (mostly with the same HAL but some mass storage devices may interfire too).

    wim technology is much better than cloning (Ghost like apps) entire drive or disk.
    Basically it's the same technology: system in WIM file was pre-installed, syspreped and cloned into image. When using Ghost there is no sysprep. But as I remember some versions of Ghost included the utility to change SID?

    WIM has its own pluses but in this case it's just clonning with Ghost like apps :whistle:

  6. Downloaded .NET Framework version 2.0 (x86) redistributable package (23MB), installed. nLite works.

    I tried so far:

    - install first nlruntimer3.exe than RC2;

    - install first RC2 then nlruntimer3.exe;

    - instoll first nlruntimer3.exe than RC2 and at last installed nlruntimer3.exe the second time (reinstalled);

    - instoll first nlruntimer3.exe than beta than RC2;

    -- instoll first nlruntimer3.exe than beta than RC2 and at last installed nlruntimer3.exe the second time (reinstalled);

    So RC2 + nlruntimer3.exe doesn't work in any variant and the problem should be in nLite (nLite-1.4.beta.exe + nlruntimer3.exe = works or RC2 + FULL .NET Framework v2.0 = works).

  7. Still the same error as before (last time mentioned by korri a couple of posts above.

    Previous version nLite-1.4.beta.exe + nlruntimer3.exe worked.

    Installation on a "clean" system (just restored from backup image).

    Have not tried full Framework install.

    Windows XP SP2 x86 English.

  8. You won't have the latest MSN Messanger in Windows 2000 (I use Miranda + MSN plugin). Some newer games maybe won't work (not much though and some of them won't work in XP too). Maybe some software and drivers won't work but usually everything working in XP works pretty well or could be moved to W2k (some manual work with files may be needed).

    Unfortuanately Windows 2000 can't be booted in RAM as XP (using only one file from Win2k3) :(

    Well, Vista is not as good as should be. XP support will last longer (not only by MS but for third party companies and individuals).

    Other than that I can't see other drawbacks of Windows 2000.

    But if you have time for tuning you may go for XP - basically it's W2k + a lot of useless crap :angry:

    And if you have more time :rolleyes: go for Win2k3 - it's something between W2k and XP but tuning it takes really a lot of time and efforts (do you think it's worth? :wacko: you may go for Linux then :)

  9. conexant hd audio and hdaudio soft data fax modem
    And I still beleive that this hotfix should solve the problem. Please note that there are a few versions of this hotfix (for different Windows versions).

    The problem may be in wrong drivers (I have a similar problem with Toshiba Satellite L401 - comes with Vista and no W2k or XP drivers :blink: Had to find them myself and still have a couple of issues (no big deal but...).

    If you want it, you may also try to change HAL: open folder WINDOWS\INF (it's hidden!), find and delete HAL.PNF (NOT HAL.INF but HAL.PNF!!!). ONLY after that try changing Computer type in Device manager (I think you know how to do it?).

    Or why not reinstalling it and trying it again? :whistle:

  10. Framework issue.

    Have the same error as jimmany in Post 51 on the second picture.

    XP SP2 English (x86).

    First installed nlruntimer3.exe, then nLite-1.4.rc.exe (SFX version).

    Was good with the same nlruntimer3.exe and nLite-1.4.beta.exe (SFX version).

    Shall try restore backup image and test again.

  11. I understand what's happenning ;) That is why I asked if it is possible to have only NET installer (that runs totally in virtual temporary evnironment ;)

    My logic:

    1. nLite needs NET.

    2. nLite installed, NET is not installed.

    3. There is a NET installer that can be run before running nLite so the last one thought this computer has NET installed.

    I'm not sure about the 3 statement so I asked :rolleyes:

  12. Interesting :thumbup

    But why you are still integrating nLite? If next version will be out should be re-do all this operations again? Why not to do it only for NET? ;) For example, use %ProgramFiles%\nLite folder insted of %ProgramFiles%\nLite-1.4.beta. Will it be possible to use this portable NET installer with the following versions of nLite? :rolleyes:

  13. 5.settings to define custom page file , size and location.

    It could be interesting feature: Windows Fundamentals for Leagacy PC has only 40MB page file during and after installation (original Windows has 40MB during installation and than relocates more according to the memory available).

  14. No need to redistribute with nLite. Why not to make Framework part portable alone? ;) If it's working I don't think somebody will be agains it. And you don't need to redistribute it too: describe the method here and we try :rolleyes:

  15. Interesting app :thumbup

    Frankly speaking that time I mostly copied and pasted the methods described by Gosh and Bilou Gateux :blushing: I often have some ideas but I don't have enough knowledge or skills myself.

    I'll try this app in a couple of days (I hope to have a few days off nearly). You can compare included INF file with the INF from the first post - the meanning is the same but in other words (apps INF installs service on the fly but INF from the first post writes the keys of already installed service). I think it should be easy to convert apps INF to INF working with HFSLIP.

    PS By the way, there is one more very interesting virtual disk that may be of some interest for you - ImDisk. It can be installed easily and turned on/off at any time. Not sure it can be used for placing temporary files (not tried yet) but it's very handy for mounting all kind of disk images (ISO, IMG, NRG and many more including images of virtual machines).

  16. I can't be sure for 100% here but I think I know the reason: switch your system language to Chinese Traditional then and you will be able to see the tracks ;) I even think if you need ST that would be more universal then Chinese Simplified - both should be displayed well after switch.

    And if you don't use Chinese Traditional input locale just delete it from keyboard settings (leave Chinese Simplified if you only use it).

×
×
  • Create New...