Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

johnny44

Member
  • Content Count

    14
  • Joined

  • Last visited

  • Donations

    $0.00 

Community Reputation

0 Neutral

About johnny44

  1. Thanks m3n70r. I think Powerpacker uses cdimage.exe to create the ISO file. It probably uses the -oc or -oi switches which are used to optimize. I guess the big difference makes sense to me now since most of the files are duplicates. The only remaining question is, if it skips duplicate files what does it put instead? A pointer to the location of the file it kept?
  2. Just a quick question someone might be able to answer. I built 8 different XP installations that total 3.3GB. When I burn the ISO, it is 1.3GB. Everything works perfectly. Why is the ISO file so much smaller? Are the duplicated files overwritten? Does it only add pointer to duplicated files? Thanks
  3. I confirm this bug. IDENT files are correctly copied to the ROOT/XP.. folder, but only the files from the first CD you build are copied to the root of the CD. If you start from scratch and build an xphome CD followed by an XP PRO CD, WIN51IC files will be in the root of the CD but not WIN51IP files and vice versa. Files from the 2nd build need to be copied to the root of the CD manuallly
  4. @bitmonster I'm not sure your make_add subroutine can add the Highmat CD update. This update is not the same type as jviewer and langpack so it does not use the same switches. When I run your make.bat file, the application switch messagebox pops up when it gets to the Highmat update. You seem to say it works for you, I am doing something wrong?
  5. From a different post by jimba: That's where the problem was! I replaced CALL XPCPRVAR by CALL :SETVARS. and I also removed CALL XPCTVARS since it is created by XPCPRVAR. Why isn't there more people complaining about this?
  6. I am too using a french version and I get similar errors(not every time though) even when the antivirus is disabled: TEMP\CATEXT\empty.cat - Le processus ne peut pas accéder au fichier car ce fichi er est utilisé par un autre processus. TEMP\CATEXT\_sfx_0006._p - Le processus ne peut pas accéder au fichier car ce fi chier est utilisé par un autre processus. TEMP\CATEXT\_sfx_0006._p - Le processus ne peut pas accéder au fichier car ce fi chier est utilisé par un autre processus. TEMP\CATEXT\_sfx_0008._p - Le fichier spécifié est introuvable. TEMP\CATEXT\_sfx_0011._p - Le fichier spécifié est i
  7. @midiboy Just to let you know you're not alone. Ever since the beginning I have to bring back my original I386 folder because the second time I run it, my txtsetup.sif gets screwed up. From the fresh install I also get the dac960nt.sys error. All I do to fix this is open my ISO file with WinISO, choose file, properties and select Joliet CD format. I save the iso and then it boots perfectly. Weird huh? Better than this, it also works if I convert all files to uppercase. On top of that, like you said, converting to uppercase fixes the txtsetup.sif error on later slipstreams. I'm using XP Pro i
  8. I forgot, my txtsetup.oem file is in the same directory as all the other files: $OEM$\$1\Drivers\P5GD1\ITE8212
  9. I did modify my winnt.sif, just forgot to mention it. Can you explain, because I kind of felt the same. This is my first time doing this so I followed this guide which is basically a detailed explanation of greenmachine's procedure. what I personally thought was that if I put the files in the $OEM$ folder and referenced it in the winnt.sif, everything was good. I also thought that if I compress the files in the I386 folder and modify the txtsetup.sif I didn't need the files in the $OEM$ folder. Maybe this works because the information is there twice. Btw, i visited btsunattended.net after re
  10. Just did exactly that with the ITE8211/12 driver. I followed Raskren's guide and copied only the files from the XP folder as well as txtsetup.oem and iteatapi(no extension) from the root folder to $OEM$\$1\Drivers\P5GD1\ITE8212. iteatapi.sys iteatapi.inf iteatapi.cat iteatapi txtsetup.oem I then compressed the first 3 files in the I386 folder and modifed TXTSETUP.SIF accordingly using the info from the txtsetup.oem. Last but not least, I modified the txtsetup.oem file to reflect the changes. I don't know if it was necessary since I think only the 3 files from the I386 folder are used to instal
  11. Didn't try the patch with XPCREATE yet, but installed it on my PC and I couldn't open a new window in IE. I tried shift+click and "open in new window" from the right-click menu and each time the actual window would freeze and the new window would never open. tried registering all the DLL's and no luck. After uninstalling it, everything came back to normal.
  12. Hi Bilou, After many retries here's where I'm at. My problem came from the fact the when I created my Iexpress package for IE6SP1, I forgot to put the /q:a /r:n after setup.exe. At the next retry I started getting the rundll32.exe error when IE6START was executing. After reading many threads, I ended on a solution with IE6_ROE.CMD from AirmaleDFW, which registers the registry keys manually. That came up pretty clean without errors. I then downloaded scriptfr.exe to solve the 814078 problem. Now, my only problem comes from KB841356. I installed it by adding it manually to the svcpack.inf file
  13. This is my first try using XPCREATE and I'm having difficulties with IE6 and windows 2000. I created my own IExpress package for IE6 and when the installation gets to IE6 I get a message saying that a previous installation needs rebooting and that the installation will be stopped. Here is my svcpack.inf file. Dotnetfx and dx9c are the only things installed before IE6 and they are run with the switches to prevent reboot. Do I need to modify the installation order or does the problem come from my installation packages? [Version] Signature="$Windows NT$" MajorVersion=5 MinorVersion=0 BuildNu
×
×
  • Create New...