Alps

Member
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Alps

  • Birthday

Profile Information

  • OS
    XP Pro x86

Recent Profile Visitors

403 profile views
  1. Thanks for having shared the link to Universal Extractor installer, Acheron! Just downloaded and installed. Then in a few seconds I created a folder with svcpack.inf and added the line to install the recovery console during setup. I hope this will work. Do you know whether RVMI doesn't recompress svcpack.inf file? If not, could HFSLIP (last version) be the best solution to overcome the recompression issues? Does it still work only with the English version of Windows?
  2. Hi Acheron! I was wondering whether svcpack.inf is created by nLite (or RVMI) or must be manually created and modified, inserting all the content of svcpack folder (in my case, about 180 items!) and other information line by line. I tried to open svcpack.in_ with notepad but there is no readable line. Is there a way to avoid typing all manually in this svcpack.inf?
  3. Thanks again, Acheron! I'll follow your clear and useful recommendations: out legacy modem drivers (adding mdmcpq.inf to the exclusion list), legacy isdn support and drivers, legacy printer drivers (using your printer driver keep list) and Windows upgrade support. I'll avoid CPU Driverpack, along with the ones too heavy (Sound and Graphics above all). As far as the recovery console is concerned, I was wondering where the SVCPACK:INF file is. In i386 folder? Perhaps SVCPACK.IN_?
  4. Thanks for all the tips, Acheron! I've had a look at driverpacks forum and I think I'll include these particular packs: DP_MassStorage_wnt5_x86-32_1412115.7z (10.5 MB) DP_MassStorage-Utils_wnt5_x86-32_1411021.7z (573.02 KB) DP_Chipset_wnt5_x86-32_1412311.7z (4.43 MB) DP_WLAN_wnt5_x86-32_1501231.7z (23.78 MB) DP_LAN_wnt5_x86-32_1412311.7z (12.26 MB) DP_LAN-Utils_wnt5_x86-32_1412221.7z (15.94 MB) DP_LAN_USB_wnt5_x86-32_1412241.7z (6.29 MB) In addition, always using driverpacks Base, I'll put the 32bit Intel MSM textmode driver (mod+signed by Fernando) in the 3rd party driver folder. This is to avoid the risk of a BSOD when I get my XP installed via VirtualBox (http://www.win-raid.com/t22f23-Guide-Integration-of-Intels-AHCI-RAID-drivers-into-a-Windows-XP-W-k-W-k-CD.html). As you clearly pointed out, it's better not to remove the original LAN and WAN driver packs because the latest ones from driverpacks website don't include any default XP driver but just updates. Precious information your printer driver keep list (containing even 3 files to remove): I'm gonna copy and paste it in nLite! But you wrote that you integrated Ricktendo and YumeYao's Common Printer Drivers and XPS Addon 1.2.3 after removing the Printer drivers by nLite to keep printer support. My intention is to only integrate the drivers of my current printers. After having done this and removed default printer drivers (saving your keep list), do I still need to integrate the drivers and addons you integrated (Ricktendo, YumeYao, XPS addon 1.2.3) in order to keep printer support? As far as ISDN and modem drivers are concerned, I'm gonna keep both of them. I could need ISDN support somewhere despite the fact that my current ISP provides DSL services. Since I don't want to run into issues by removing legacy modem drivers (as you said it happened to you with your old Nokia), I keep the default modem drivers: along with the ISDN ones they are just about 15 MB. Following your suggestions, I'll remove the drivers you mentioned (keeping Sony Jogdial support, just in case...). As far as windows upgrade support is concerned, does its removal affect windows updates service? I still receive automatic updates (the POS ready ones) and so far I've never experienced any issue regarding OS instability. That's why I prefer to keep the automatic updates. You then mentioned the recovery console support. As far as you know, is there an addon to get this recovery console installed with XP without the need to manually install it lately?
  5. Excellent help, Acheron! Thanks for your useful suggestions! I've just checked the last version of MassStorage Driver Pack from http://driverpacks.net/downloads and it seems that this file is the most up-to-date: DP_MassStorage_wnt5_x86-32_1209.7z But you wrote "the latest MassStorage Drivers 14.11.191". Did you find them on driverpacks.net or somewhere else? Glad to know that I should have 200 MB left for integrating drivers! So I won't have any space problem if I integrate CPU, Chipset, MassStorage, LAN and WAN drivers. For these last 2 packs, would you recommend to firstly remove the ones coming from the XP SP3 I386 folder (less than 3 MB as nLite indicates), before integrating LAN and WAN packs from driverpacks.net? You said you had removed a lot of legacy drivers. Actually, I wish to remove many legacy drivers as well: "Cameras and Camcorders", "IBM PS/2 TrackPoint", "IBM ThinkPad", "Logitech Wingman", "Microsoft SideWinder", "Printers" (nLite suggests to keep just a specific file needed for PDF printers, do you know its name?), "Scanners", "Sony Jog Dial", "Toshiba DVD decoder card". Do you have a similar list of removed drivers? But I wish to keep other ones: "ATM", "Display Adapters", "Multifunctional", "Portable Audio", "SCSI/RAID", "Serial Pen Tablet", "Sound Controllers" and "Tape Drives". These all count just about 5 MB. Would you instead remove some of them? Why? Finally, would you even remove "ISDN" and "Modems" drivers? They count more than 15 MB but I'd like to keep them. After all, I have a 56k modem integrated in my old laptop that I can use in particular but possible occasions (with router and ADSL modem out of order).
  6. Thanks for your replies! My intention is just to create an installation cd suitable for latest and oldest computers (from 2004 like mine). In the latest machines I could run WinXP simply via Virtual Box: it's convenient in order to avoid rebooting PC (because of using another partition with WinXP). RAM is quite abundant nowadays, so Virtual Box (or similar) can easily manage this task. My preference for CD comes from the incompatibility with USB installation (old motherboards, like mine, don't support it) and even from lack of DVD writer (or its malfunction). My questions were related to computer's components, more than peripherals (printers, scanners, etc.). I mean HD, CPU, GPU and so on. And I heard that Chipset, Mass Storage (for SATA HD), CPU, LAN and WLAN driver packs are enough to successfully install WinXP on many of the newest machines (in a dedicated partition or even via Virtual Box). You know it's time consuming to create a customized installation disc so I'd like to create just one 700 MB disc. After all, WinXP is very slim and it shouldn't be so difficult to keep it under 700 MB (including updates, hotfixes, peripherals' drivers and software and some utilities, the so called "addons"). But I need to know what is superfluous and completely unuseful and what should instead be kept. That's why I posted these messages and I hope I'll manage to create my slim installation disc with your precious support.
  7. Hi folks! Many people suggest to include at least Chipset, Mass storage, CPU, LAN and WLAN packs in a customized installation cd of WinXP. Firstly, WLAN pack in Driverpacks website is almost 30 MB, instead nLite shows a 1 MB pack (from WinXP SP3). Can I just keep the last one (for cd space reasons)? Will I face incompatibility's problems with the latest PCs in this case? Secondly, DriverPacks provides about 12 MB of LAN and LAN-RIS drivers, while nLite shows 1,84 MB of LAN drivers. What if I keep the 1,84 MB of LAN drivers and then integrate the 12 MB packs? Will 1,84 MB be overwritten by the 12 MB packs? Or, more simply, do the 12 MB packs already include the older 1,84 MB pack (so I can safely remove the 1,84 MB)? Apart from the above mentioned driver packs, there are quite heavy driver packs on DriverPacks website. I don't think those packs are suitable for a 700MB cd with WinXP SP3, updates (including POS ready ones), hardware drivers and software (scanner, printers, internet keys, etc.). But as far as you know, would I need other driver packs if I wanted my WinXP correctly running on almost all the latest computers' hardware?
  8. Hi everybody! I'm trying to slim down Windows XP with nLite and I'm facing some driver's issues. This is the drivers' list: Asynchronous Transfer Mode (ATM) – 150 KB Cameras and Camcorders – 1 MB Display Adapters – 10,24 MB Display Adapters (old) – 1 MB Ethernet (LAN) – 1,84 MB IBM PS/2 TrackPoint – 50 KB IBM ThinkPad – 2,50 MB ISDN – 5,77 MB Logitech WingMan – 30 KB Microsoft SideWinder – 100 KB Modems – 10 MB Multifunctional – 60 KB Portable Audio – 250 KB Printers – 33,74 MB Scanners – 7,22 MB SCSI/RAID – 500 KB Serial Pen Tablet – 20 KB Sony Jog Dial – 150 KB Sound Controllers – 4,18 MB Tape drives – 40 KB Toshiba DVD decoder card – 350 KB Wireless Ethernet (WLAN) – 1,00MB After some research it seems that many prefer to remove all drivers except for a few ones like display adapters, LAN, portable audio, WLAN. Considering that I'm concerned about saving MB but even creating a quite “universal” XP cd, I would even keep ATM, Multifunctional, Portable Audio, SCSI/RAID, Serial Pen Tablet, Sound Controllers and Tape Drives: they all count just about 5 MB. Do you agree? If not, what would you remove? And why? Then I have some doubts about ISDN, Modems and Printers. I usually have a wireless internet connection and in rare occasions I need to use the ADSL modem but this has its own driver. Very rarely, in cases of ADSL fault, I use the 56 KB integrated modem in my laptop (just to read e-mails). Could modem drivers turn to be useful on these occasions? So why not keeping them? Even because DriverPacks website provides a 25 MB modem driver pack, while I currently have just 10 MB as nLite shows: 15 MB cd space saved in this way. What do you think? And what about ISDN? Why remove it? Are they too old for the latest computers? Lastly, as far as printer drivers are concerned, I would remove it but nLite suggests to keep a specific file needed for PDF printers (Advanced – Keep Box). What is this file?
  9. Sorry, I forgot to mention another component: NT Backup. It's written in red, so it should be a critical component because of its dependencies. I should keep it, shouldn't I?
  10. Thanks a million for your clear explanations, GrofLuigi! Actually, I've heard something on the importance of the defragmenter (and possible dependencies) but I really didn't know about this sort of indirect dependency between paint, image filetypes and WinXP components. So, I'll follow your advice and keep both of them (defragmenter and paint), along with Charmap, Screensavers (they're just a few MB) and File Sync. Finally, let me remove a small doubt regarding Clipbook Viewer. If I'm not wrong, you said that clipboard functions (cut/copy/paste) are removed along with Clipbook Viewer. But I was thinking that I often take screenshots. Pressing "Print Screen" key makes Windows copy the entire screen to the (invisible) clipboard and then I paste it into Paint. Does the Clipbook Viewer's removal undermine this functionality?
  11. Hi everybody! I got 8 WinXP PRO applications which nLite showed me in the components' removal. These are: - CALCULATOR - CHARMAP - CLIPBOOK VIEWER - DEFRAGMENTER - PAINT - SCREENSAVERS - WORDPAD - FILE SYNC I found a couple of addons which could effectively replace calculator and paint: microsoft calculator plus and paint.net v. 3.5.11. Then, a useful utility could be MyDefrag v.4.3.1 (addon in cab format). But many leave the default defragmenter where it is. Do you think that I could eliminate defragmenter without any adverse effect? Leaving the unuseful Wordpad out, what would you advise on the remaining applications? Charmap, clipbook viewer, screensavers and file sync are removed by many people. Would you save 1 or more of them? Why? Or why would you remove them? Which would you remove? And which addons would you advise for replacing them?