Jito463

I hadn't tried with a winnt.sif set to OEMPreinstall=No - for what I was doing, the OEMPreinstall was the only reason I needed the winnt.sif - so you could be right.

Unfortunately, no. As I discovered after making a disc with only SATA drivers loaded from $OEM$ and found out I couldn't repair installs because of it.

Meh, it just struck me as funny. No harm meant.

That's odd, because I have a retail copy of Ultra Edition (never even heard about Enterprise edition until this forum) and I have both NeroNet and the option to burn to multiple recorders. This is what it says on Nero's website about Enterprise Edition:

Yep. Precisely my point. Thanks for making it for me

If you have a winnt.sif with OEMPreinstall=Yes, then you will not get an option to repair the install.

Very nice. I've been trying to figure out a way to do this for a while now. Thank you.

Why don't you create a reg key that will change it automatically, then silently run it before the install?

Sorry, I couldn't resist

Must? I don't know about that. That's just preferences. You can set them in the reg file, or set them from within Nero. As for NeroCheck, I used to disable it, but I'm beginning to think it's better to let it run, as it's sole purpose is to ensure that neither Nero nor any other program screw up your filters entries (like Roxio 5 did when it first came out). So it's actually a good thing.

Nope, it works with any valid Nero 6 key

Kind of defeats the purpose of an "unattended" install, but I suppose it could be done like so: IF NOT EXIST %CDROM%\xxxxx.txt GOTO INSCD :INSCD ECHO. ECHO Please insert CD 2 PAUSE IF NOT EXIST %CDROM%\xxxxx.txt GOTO INSCD IF EXIST %CDROM%\xxxxx.txt GOTO INSTALL :INSTALL %CDROM%\whatever :FINISH ECHO. ECHO Please insert Windows Unattended CD-ROM PAUSE IF NOT EXIST %CDROM%\win51 GOTO FINISH IF EXIST %CDROM%\win51 GOTO QUIT :QUIT EXIT Now, for that to work you'll need some way to define %CDROM% and replace xxxxx.txt with whatever file you want. But that should do it. I haven't tested it, mind you, but it should.

It's possible you keep getting the same reg entry because you're using the same key. One possibility anyway.

That is *way* too much information

Or just setup a batch file to copy from %AllUsersProfile%\All Users\Application Data\Microsoft\User Account Pictures\Default Pictures\whateverpicyouwant.bmp to %AllUsersProfile%\All Users\Application Data\Microsoft\User Account Pictures\%UserName%.bmp (it will automatically supply the current users name for %UserName%)

Just save it as a shortcut (.lnk file) and direct the scheduled task to the shortcut.

I'd be interested in the *HOW* of this. I believe he meant Task Scheduler, which is simple. I use Task Scheduler to open a flash file (this one here) at predetermined times to wake me up. But you can use a music file, or even a URL to an online music station. Whatever you want. 1) Open Control Panel and double-click on Scheduled Tasks 2) Right-Click anywhere and select New -> Scheduled Task 3) Rename the new task to Alarm Clock (or whatever you want) 4) Now double-click on it to get to the properties page 5) In the RUN dialog, click browse and browse to your media file or .lnk file. 6) Once done, make sure "Enabled" is checkmarked and click Apply, type in your password for Windows when prompted (if you have one) 7) Click on the Schedule tab and set the times/dates you want it to run. I also go into the Advanced setting and have it go off every 10 minutes after that time until either a specified time or for so long then stop. 8) I usually head to the Settings tab at this point and under Power Management I check/uncheck the following settings: |_| Don't start the task if the computer is running on batteries |_| Stop the task if battery mode begins |x| Wake the computer to run this task There you go. A fully functional alarm clock using Task Scheduler.

That's what I do. I mount it to Alcohol's VD and then capture it in VPC. Works great.

You've either got a really bad stick of RAM or the CPU is toast. Best to swap out the RAM first, as that's the easiest to test. Oh, FYI. Regarding the RAM running at 266. Your CPU's FSB is 533, which is 133 "quad-pumped" (133 x 4). Since your RAM is DDR (Double-Data Rate), it's running at 133 x 2 (266). 133 - though - is the actual FSB. This is probably why your RAM is running at that speed.

@MCT For what he has, 350 is enough. If he starts adding a lot of stuff to his machine then he might need to upgrade, but what he has will work fine. @Philliman You're probably looking at either CPU, RAM or HDD. You could try swapping out your IDE cables, too (and make sure the ones for your HDD are 80-wire. e.g. ATA66/100/133). If swapping the cable doesn't do the trick, there's some tests you can run to test your components. Memtest86+ Ontrack DataAdvisor One thing to keep in mind is, if Memtest comes up with errors it could be either CPU or RAM. A bad CPU can cause errors in Memtest just as easy as bad RAM, though it won't necessarily do that.

D'oh! I just read that in your post, prathapml. I hadn't seen it the last time I read through.

That's correct. The files are identical, but if you install from CD, it MUST be named winnt.sif or the Windows install doesn't use it.

Try adding this to your Components section of your winnt.sif: [Components] IEAccess="Off"

Try: AllowedPrograms = WindowsFirewall.NDPS PortOpenings1=WindowsFirewall.VNC PortOpenings2=WindowsFirewall.RPM See if that works.

I think I'll wait for the official release. 6.3 works fine for me atm, so no need to rush for the latest. I'll let them get the bugs worked out right and then release.