jaclaz

UNREAL Maybe you play too much games and happen to mix their titles, UBCD4Win is the Ultimate Boot CD for Windows, and it's really, really real. jaclaz

My guess is that the topic is related to "context menu" or "shell extensions" or "right click menu" or "file/folder associations". Some links/info: http://www.xs4all.nl/~wstudios/Associate/ http://students.kennesaw.edu/~rzillige/she...hext_index.html jaclaz

Yes, definitely it's the video card, possibly some RAM in it, or it can even be "main" RAM. jaclaz

Let's try and separate the two problems: a) is it legal? b) is it possible? a) depends on the kind of license you have. b) it is possible, though not easy and usually not recommended: http://www.michaelstevenstech.com/moving_xp.html I don't see why XP64 should be different from XP 32 bit. jaclaz

Rather than disabling/reenabling the devices, I would try REMOVING them. At next re-boot the System should re-detect the hardware and re-install the drivers. By any chance, did you install at any time any "Virtual Drive" related software, like iSCSI stuff, Virtual CD drivers like Daemon Tools or the like? jaclaz

Which are a mirror of the already mentioned Maximus Decim Native drivers, or nusb, that have their "home" right here on MSFN: http://www.msfn.org/board/Maximum-Decim-Na...ers-t43605.html jaclaz

I'll try again : jaclaz

Let's try again. Post the directory structure you are using, I will try and replicate it, to try and see if we can find the problem, i.e. I need something like this: C:\testmkisofs\ C:\testmkisofs\boot.bin C:\testmkisofs\mkisofs.exe C:\testmkisofs\Source jaclaz

Well, try entering BIOS, do the same lines appear? If yes, something in hardware is "gone beserk", if not it is a driver (software) problem in your Vista install. What happens if you toggle between "Internal only/External only/Both" (or similar) settings about Video output in BIOS? Try booting from CD a non graphical OS, like Recovery Console or DOS, and see if the display "behaves" or not. jaclaz

I wonder how do you expect me to have an idea of how "those nasty vertical lines" look like. How did you manage to get to "safe mode" (whatever it is) if you have either a black screen or "those nasty vertical lines"? Can you get to the BIOS? (usually is pressing DEL or one of the Fn keys while booting) Have you got a Boot CD of some kind? jaclaz

It may also be the screen. Can you try using it with an external display? I would check that first thing. (I have seen laptops that "by magic" redirected output to external VGA only) jaclaz

Most probably mkisofs makes a check on the boot file and needs also the "no emulation". The "default" to make a XP boot CD "should" be the following: (this is "hardcoded" to M: drive) Can you just try to run the above? jaclaz

The filesystem appears to be OK, as TESTDISK reported. The 0x0000007b then must be a driver, missing or corrupt. Is it a SCSI or SATA drive? I don't think the hard drive is bad, usually that would prevent also Linux from working, but in some - VERY rare - cases a corruption of just the MBR or boot partition may prevent a Windows based boot CD to work. However, there is no apparent reason why a boot CD won't work. Try again with your boot CD or make a new RC one as per links in point 3) of my previous post. See what CHKDSK says. jaclaz

In your example, boot.bin has to be in the same folder where mkisofs.exe the source is, or the path to it must be given. A good idea is to use, until you have mastered the command line options, to use a GUI or pseudoGUI for mkisofs. Check this thread where the matter about the path is explained: http://www.911cd.net/forums//index.php?showtopic=16997 And, if you are making a "normal" boot CD, maybe this is handy: http://www.boot-land.net/forums/?showtopic=4425 jaclaz

Yep, the point is how would you put a remedy to it? I mean, opening the Hard Disk to vacuum clean the platters it's NOT exactly a good practoce. jaclaz

.inf files have the same "structure" as old .ini files. This is a good start point: http://www.robvanderwoude.com/batchtools.html Though it is possible to use a "pure" batch solution, here is an example for reading .ini files from batch: http://www.robvanderwoude.com/batexamples_r.html#R the use of the program from Horst Schaeffer or a similar one is much easier. jaclaz

Every "major" OEM does changes, and they are even often NOT ALL the same ones from a same OEM, even the "philosophy" of the changes different models/releases of the disk. Of course supporting (in the sense of being compatible with) all these different releases would be a nightmare, and nuhi instead of the GOOD "lone" guy he is should be a Corporation. For the same reason it is practically impossible to say WHAT is the thing (orr things) that break the compatibility with nlite What you can do is "revert" the concept: create from the files you have and from the Service Pack(s) or other files provided by Microsoft, adding drivers and (if wanted) "OEM apps" from the files you have or from the Manufacturer's site, a "standard" build. See this thread: http://www.msfn.org/board/How-do-I-make-a-...th-t120423.html AND the ones there referenced. Of course a VM for testing is needed, at least initially, and however some tests with real hardware are needed anyway, you should use a CDRW as the making of a few coasters are probable during the process. Once you have a working "standard" CD, you will see that nlite works perfectly. jaclaz

No prob. The good news is that there are a few reports that the semi-automated method based on "fake signature" or "XP Kansas City Shuffle" work allright, I think now it's time to begin thinkling about labeling it more "Beta" than "Alfa-Alfa", get the batch from cdob here: http://www.911cd.net/forums//index.php?sho...c=21939&hl= http://www.911cd.net/forums//index.php?sho...c=21965&hl= RAMDISK booting is a completely different topic, it requires some Server2003 SP1 or R2 files (and thus a WHOLE Server2003 license according to MS licensing scheme) or the use of third party applications, much cheaper than a Server 2003 License but I do not think it could be the "right" solution for your needs. Anyway if you want to explore the matter, just ask and I'll give you some more links. Yes, it's a bit complex, and probably not worth the amount of work involved. [italian] Diciamo Commercialista/Consulente del Lavoro/Ufficio Paghe per capirci. Buongiorno Ragioniere (o Dottore ) [/italian] Yep, been there, done that. EVERY single program of that kind is (POORLY) designed and the software house has the arrogance to ignore the fact that it should be able to live side by side to ANY other program or "protection". Not to demonize an entire category of professionals, but yes, I have seen myself that a number of them, expeciallly in country towns/villages, can be like that. Also been there, done that. So, all the problems is to be able to get a week off the office and be able to sleep without worries, is it? Yes, I feel for you, I perfectly understand your situation, not very unlike mine, and, if I may, you seem the first "Accountant" or "Consultant" I've ever met that is actually AWARE of the risks connected with loss or unauthorized distribution of "sensible" data. Yes, this can be a good solution, though, in a "professional" environment, I would also think about some forms of network based install/backup/imaging/restoring and using a Server or NAS for the actual data. Also, an option that could, at least partially, solve the problem of "multiple" computers could be that of multibooting the same PC with different installs, and/or making use or Virtual Machines (though the latter approach may turn out to be not doable because of hardware "protections" - USB, serial or whatever) Cheers, jaclaz

No need to enable extensions, if you use instead of neq IF NOT no need for ELSE, at least not in the snippet code posted. Try editing as below: if NOT "%COMPUTERNAME%"=="ME" ( ECHO INSIDE IF&PAUSE echo Adding your Credentials informations in storage of network password ECHO INSIDE IF BEFORE START&PAUSE start /wait Settings\cmd\AddCredentials.cmd ECHO INSIDE IF AFTER START&PAUSE ) ECHO PAST IF&PAUSE What output you get? jaclaz

Typically 0x0000007B means "inaccessible boot device", usually a missing/wrong MASS STORAGE driver for the BOOT HD, a defective cable, a bad HD or a corrupted HD. A possible troubleshooting path (after having DOUBLE checked cables and connectors): 1) run from Linux TESTDISK: http://www.cgsecurity.org/wiki/TestDisk it may be able to fix the problem at least to a level where the booting from CD works 2) DO NOT try booting Windows after TESTDISK did (hopefully) some fixes, rather try again: 3) boot from CD and run in first instance CHKDSK with NO parameters from Recovery Console, MAKE SURE that the CD RC does contain AUTOCHK.EXE, otherwise you need first thing to have a CD with it, see here: http://www.boot-land.net/forums/?showtopic=5316 (and links within) 4) If CHKDSK reports no errors, you may try booting from HD, if it does: 5) Run CHKDSK with the /F parameter 6) 4) If CHKDSK reports no errors, you may try booting from HD, if it does: 7) Run CHKDSK with the /R parameter Report if anything goes wrong. jaclaz

You're welcome. jaclaz

Sure , were you doubting it? jaclaz

Why the name needs to be the same? CD FX\LEET REN leet l33t MOVE l33t .. cd .. RD /s /q LEET REN l33t leet Or: CD FX REN leet l33t MOVE .\l33t\LEET . RD /s /q l33t jaclaz

Also, INSTEAD of "safe mode", I would try the /BASEVIDEO switch in boot.ini: http://technet.microsoft.com/en-us/sysinte...s/bb963892.aspx alone or together with /SOS and /BOOTLOG You can use the Linux install to see the contents of %SystemRoot%\Ntbtlog.txt, though often it does not help much. jaclaz

Basically the usual approach, that can be easy or difficult depending on the actual OEM CD and the amount of mods the OEM made is to re-build a "standard" CD out of the files on the Recovery CD, see these: http://www.msfn.org/board/Help-restore-cd-...ons-t70301.html http://www.911cd.net/forums//index.php?showtopic=16381 http://www.msfn.org/board/Cannot-access-CD...P-i-t91907.html The post at neowin can be viewed from here: http://web.archive.org/web/*/http://www.ne...07&t=386271 http://web.archive.org/web/20060405155342/...07&t=386271 jaclaz