Jito463

You know, it's so simple I can't believe I didn't think of it sooner. Maybe because it's so simple? I've been having an odd issue lately with my TechDVD where I use finddrv along with the label to find my DVD drive and set it as a variable (%tech%). That worked under IsoLinux with mkisofs. But with CDImage and CDShell, it can't find the drive even though if I switch manually to the drive my disc is in and do a dir listing it shows the label correctly. Well, duh. Here's this idea and it solves all my problems. I just created a blank file called TechDVD (no extension needed) and do: That did it. Thanks for helping me realize my ignorance And as a bonus, I even manage to get rid of an extra line, heh.

Did you update the boot files as well? You need to download the bootdisk images from MS's website and update that part.

Umm, are you asking a question or pushing the software?

Now the firewall blocks outgoing as well as incoming connections, like a true firewall. The previous version only blocked incoming connections. This is why people are having a problem with it. They're not used to a secure PC, heh.

Personally, I don't recommend Memtest86 anymore. I much prefer Memtest 86+, which is an expanded version carried on by another crew (more releases/support). They're currently at 1.26 (and they even have a version that will work from pure DOS, providing there's no memory managers loaded).

Mad: Is this your primary HDD or your secondary?

Ah, ok. I think I understand. Though you'll probably need to have more directories if you plan on having a preinstall and setup on the same disc. Even if you don't do a preinstall, the $OEM$ directory is parsed. And it must be in the same directory as i386. So you'll need a preinstall directory and non-preinstall directory for each version of Windows (one with and one without a $OEM$ directory). Everything else seems to be in the right place though, so I'm not sure why your winnt.sif isn't being parsed.

Two things. First, change this: OemPreinstall=No to: OemPreinstall="Yes" Second, do you have the winnt.sif in your I386 directory, or your boot directory in the root of your drive?

Yes, I've noticed this as well. It doesn't cause any real problems for me, but I wonder what the end-user thinks when they see all that happening I'm toying with a reg key that's implented on syspre shutdown that deletes whatever key it is that's causing this to happen. Still working on it, though. When/if I find anything I'll let you know.

Quick update. I tried recreating the image using IsoLinux and BCD (Build CD from www.nu2.nu). This worked like I expected. I tried using cdimage to create the IsoLinux image, but it wouldn't boot (some of the options must be different). Creating the image again using cdimage and cdshell failed to find the drive. I also tried changing the autoexec so it used findcd instead of finddrv, but to no avail. So, I'm stumped again. But I'm still waiting to see if anyone has any ideas. Thanks in advance.

Hmm, yes. I agree. Post it. Have you determined if it's compatible regardless of SP used (you just never know what a new SP will change and break something). And if you do figure out a way to move those files, post it. But to my knowledge it cannot be done.

What I did for my preinstall was to put the files in the path: $OEM$\$1\Windows\Web\Wallpaper It should work the other way, yes. But this did it for me. The issue I'm having right now is figuring out how to set a custom background as the default during setup so I don't have to change it post-install.

Come on, now. Why would I spend $150 for something I can do for free with other utilities? Pfft. Get real

Since the CD Shell forums are down, I wonder if you folks can help me with a little problem. On my previous TechCD, I used Isolinux and multiple boot images to fit all my necessary utilities onto one disc. This worked fine. Some of my images, even expanded to 2.88MB just couldn't hold everything needed (like Norton AV and F-Prot for example) so I put the program files on the CD and used a basic batch script from the boot disc to find the right drive and launch the utilities. But now with CDShell it won't find my disc in the path process. Here's an example of my script I used to determine which drive my disc was in: goto %config% :NAV LH MOUSE.COM LH MSCDEX.EXE /D:oemcd001 /L:J A:\FINDDRV MS-RAMDRIVE if errorlevel 3 set temp=c: if errorlevel 4 set temp=d: if errorlevel 5 set temp=e: if errorlevel 6 set temp=f: if errorlevel 7 set temp=g: if errorlevel 8 set temp=h: if errorlevel 9 set temp=i: set temp=%temp% A:\FINDDRV TechDVD if errorlevel 10 set tech=j: if errorlevel 11 set tech=k: if errorlevel 12 set tech=l: set tech=%tech% path %temp%;A:;%tech%;%tech%\cmdnav pkunzip A:\commands.zip %temp% autoscan.bat GOTO QUIT Now, the reason for such lengths was because if the computer had two drives in it, I wanted my script to easily determine which drive had my TechDVD in it. The first finddrv part is obviously for the RAM Drive that I setup in the config.sys. The second part is for my TechDVD as the label is "TechDVD". This worked under Isolinux, but not under CDShell. When I do a path after booting I get: path=C:;A:;;\cmdnav It should be: path=C:;A:;J:;J:\cmdnav Does anyone have a reason why finddrv isn't finding my drive? It finds the RAM Drive and sets the path accordingly (%temp%), but not my DVD drive (%tech%). The drive is definitely there as I can access it by switching to the J drive manually. And a directory listing shows the label as TechDVD so it's all correct. I've attached my autoexec.bat and config.sys in the rar file if someone wishes to take a look at them but this has me confused. If someone has an idea as to why this isn't working I would greatly appreciate it. Thank you.

Yes, that should work fine, but don't forget to add it to your txtsetup.sif and put the files in your i386 directory to make it find the drives when booting.

I work for a small OEM, and we install AVG 6 FE on new machines as a basic AV for the customer. I, too, have been having issues with the preinstall. If anyone could assist in this, I would greatly appreciate it. Is it possible this method only works for the pro version, and not the free edition?