prathapml

That is when you have made your unattended CD - or you're using one made by someone else. In this case, he had used a normal CD, and manually input his key - so it won't be there in that file (plus, he doesn't want to take out his original CD). Could you please tell at what location in the reg you can find it? 'Coz AFAIK, all windows OSes since win2k (win2k,winME,winXP,wS2k3) do not store the key in human-readable format in the registry.

Even if you're both italian, please remember that this is an english-language forum.

Try checking whether your directX installation is fine, and up-to-date. And then whether your drivers are all the latest possible version. And lastly, that you have the minimum hardware required.

I think I understood what jaclaz was saying... He is mentioning a lot more advanced thing - about how to run win95 *DIRECTLY* from a CD. Whereas, I think pantapei is mentioning something else: Pantapei wants to pick-up his win95 (original) installation CD, and make it bootable so that he won't need to first boot from a floppy to start win95 setup. (in other words, to put a DOS emergency boot-disk as boot-sector - because the win95 CD is not a bootable CD, whereas win98 CD is bootable).

yes, its perfectly possible. Here's an outline of how: 1. Install win95 normally. 2. Make a startup-boot-disk of win95 (or bootdisk of win98 is better). 3. Now keep the floppy-disk in the drive. 4. Install Nero (for CD-writing). 5. Start it, and go to File >> New. 6. Scroll-down in left-pane and choose "CD-ROM (Boot)". 7. In the tab for "Boot" choose your A: drive as boot-image. 8. Now add the win95 CD's entire files/contents (or whatever you want). 9. Write the CD. That's all, there you have it. NOTE: I've noticed that if you're writing a bootable CD, then writing to it at 24x or lesser speed is the best. If you burn at higher speeds, the CD doesn't always boot properly.

You're right Adiel. You need to use folder names like "Windows" or something (or whatever you want the folder to be named).

Yes, it works that way.

StarWars is great - all the way since the eighties!

If its still not solved, try with v1.00 - then you'd know if its a version-regression, or a user-error.

On Wednesday's press conference, O2 showed their next Pocket PC Phone Edition device, the Xda IIi, first time publicly. Basically, as previously said, the Xda IIi comes in the same housing as the previous Xda II and the differences are in the details. - includes an Intel Bulverde CPU, running 520 MHz - supports W-LAN - supports Bluetooth using the Widcomm Bluetooth stack, already introduced with the Xda IIs/III - includes a 1.3 Megapixel camera - will be released with Windows Mobile 2003 Second Edition for Pocket PC Phone Edition containing AKU2 which supports Windows Media 10 Mobile -------- O2 Xda IIi - it looks like Xda II but has Wi-Fi, faster processor and megapixel camera It looks like XDA II, feels like XDA II but is not XDA II! It's XDA IIi ! O2 Europe announced upcoming XDA III and XDA IIi already on September 15, 2004, but now first review appears: All together the Xda IIi is a worthy follower of the Xda II and it makes the best selling Pocket PC Phone Edition even better. Adding Wi-Fi support was a must because this was the most missing feature for most of today's Xda II users. The 1.3 Megapixel camera is state of the art for mobile phones and talking about the mobile phone features: the Intelli technology makes it a real mobile phone now - the first time I feel comfortable to use a Pocket PC Phone Edition as a mobile phone (just to make it complete: T-Mobiles MDA compact also includes HTC's Intelli technology already). A price wasn't given yet and the release is expected for end of December/during January. link to hardware review

You need the CD idents - you might have forgotten to copy the files called:WIN51 WIN51IP WIN51IP.SP1/sp2 (can also be win51ic for home edition) As for fixing the "too big" size problem, if the link by Bi0haZarD hasn't yet fixed it, then try using the optimize switch in CDIMAGE, while building your ISO image.

There's a registry tweak to turn-off notification of newly-installed apps. SEARCH!

One thing you should know, is that the cmdlines.txt file in $OEM$ folder is processed like a batch-file. And it will be processed whether you have winnt.sif or not. So, for example, if you have the $OEM$ folder in root of CD, and a folder called PLSCOPY and cmdlines.txt and any batch-file (example, FILE.CMD) inside $OEM$. Example contents of cmdlines.txt: [Commands] ".\FILE.CMD" Example contents of FILE.CMD: @echo off CLS xcopy /E /H /R /Y PLSCOPY %systemdrive% EXIT That's it. That will copy the folder called PLSCOPY to C:\ drive. I hope that the examples made it clear for use? You can add more commands for app-install, for RunOnceEX or whatever - to the batch-file.

Hey, if your problem is about having to swim through truckloads of pages to find what you want, then you can directly jump to the post that has your answer: 1. In Result Type, choose "Show results as posts" 2. If you know which member has made the post, (me normally ) then specify that in "Member name". 3. You will get many results with links directly to the post, click that: (example) i.e., Post Preview: #2199374. If you still did not reach the post that showed up, then search for your term again using your browser (press Ctrl+F, then find your word). 5. You can also use the "Print this topic" link and then use the browser search (Ctrl+F) to find what you want. Its simple actually - just like everything else, the more time you spend while doing it, the better you become.

READ THE RULES! Yes, please keep talk of cracks out of the forum.

Hey munsy, do the below to get it back: 1. Copy/paste the code below, into notepad. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\MSCONFIG.EXE] @="C:\\WINDOWS\\PCHealth\\HelpCtr\\Binaries\\MSConfig.exe"2. Now save this as "msconfig.reg" (verify that it has a .REG extension and not .TXT). 3. Double-click this file, to import the path into the registry. That's all. Hoping this helps.....

Now why's hotmail getting reminded of "The Gladiator"?

@bio-hazard That's using something called SLP-activation.If it finds a recognised BIOS id, it will get activated. If not, it won't. Google for more info!

Indeed, it disappoints the person trying to help (like Yzowl), if their posts are "skipped over" with just one chorus of:

Yeah, he's right. I just posted what I could confirm was working for me.

Nope. Dump the setup stuff. That's needed only for a manual install (which too can directly be done thru INF selection if you aren't n00b).Delete the setup stuff, and just continue your normal method (the "OEMpnpDriversPath=" method). @Lucius Snow That NRM folder can be deleted. That is the configuration folder for the integrated ethernet chip in nForce3-based MoBos (those are 64-bit boards). If you're having an nForce2 board (like me), that folder is positively a waste of space.

In other words, for every extra quote that you want to have, you need to prefix a reverse-solidus (slash).

Why isn't the search button used more frequently? This topic has been discussed before. Attached to this post, is the tool you want. Bat2Exe.ZIP

Well, then probably you have an older version.... Which Service Pack do you have installed? The command I gave above, was for SP2.

You can actually use this idea for other drivers as well, which use a pattern of *.DL_ (for example) in its files. That way, when you finally compress it, the end result is a smaller archive. ATTENTION: Bashrat the Sneaky, please do not forget to do this method, if your next video driverpack is going to contain nVidia drivers of v66.93 or higher.