jaclaz

The files are System and Hidden. If you remove the attributes you can change them allright, unless you are not Administrator and it'a NTFS volume with restricted access, however the procedure with Recovery Console is pretty straightforward. An alternative, just in case, is making a NT loader bootfloppy: http://www.tinyempire.com/notes/ntldrismissing.htm http://www.xxcopy.com/xxcopy33.htm jaclaz

The 911CD forum is back online , do read this thread: http://www.911cd.net/forums//index.php?showtopic=16381 jaclaz

Well, the idea of giving links is that people should actually read them , here: http://www.multibooters.co.uk/ you can find some very clear details on how NT/2K/XP/2003 boot and how Vista does: http://www.multibooters.co.uk/multiboot.html (even if you don't read the text, just looking at the pictures should explain what "bootsector invoking NTLDR" means ) jaclaz

It would be interesting if the guy that made you worry would produce some data to validate this claim. "this is very bad" is not considered usually technically a valid argument. I had a co-worker that didn't want DHCP to assign it's PC an IP address ending with 17, as he thought it was bad..... Maybe the claim originated by this kind of problem: http://searchnetworkingchannel.techtarget....1232847,00.html http://en.wikipedia.org/wiki/IPv4#Addresse...ing_in_0_or_255 IP addresses ending with 0 or 255 are not always possible. The only related "bad" thing I can think of is that some peer-to-peer networks had (or still have ) an algorithm to calculate ID "level" that resulted always as "LOW" if IP address ended with 0. jaclaz

Happy you made it! jaclaz

Well, this time it's (maybe first time) NOT Vista's fault. I mean a poor OS has to put it's bootfiles somewhere, and has to put them on the boot drive, and to be more exact on the first active primary partition of first drive. Most probably you can "revive" your previous operating system, (I am guessing it is 2K/XP/2003) by simply restoring the appropriate bootsector invoking NTLDR. This can be done with the utility fixboot from a XP Recovery Console (booted from original install CD) or from Vista, in this case you need to use bootsect.exe /nt52 All. The above of course only if you did not alter somehow disk order or deleted files belonging to your previous OS install. Do read here: http://www.multibooters.co.uk/ and this particularly: http://www.multibooters.co.uk/installing.html If you cannot boot any of the above, you can make yourself a WIndows NT boot floppy, just to start the PC, along these lines: http://www.xxcopy.com/xxcopy33.htm If you have problems in doing so, download grub4dos 0.4.2 from here: http://grub4dos.jot.com/WikiHome http://grub4dos.jot.com/WikiHome/grub_for_dos-0.4.2.zip? and create a floppy from fat12grldr.img jaclaz

That error is typical of missing or misplaced "tag" files, as Legoliam pointed out. Read more about them here: http://www.msfn.org/board/Edit-txtsetupsif...o-M-t65541.html http://www.msfn.org/board/XP-SP2-bootable-...in-t111302.html jaclaz

Well, how you set up your system (removing a partition and/or formatting a partition or the entire disk) is up to you, we cannot say what it would be best for you. First partition on first disk is: multi(0)disk(0)rdisk(0)partition(1) when the system is booted off the USB stick, disks are shifted up by one, same partition becomes: multi(0)disk(0)rdisk(1)partition(1) But since you have as first partition the hidden Dell one, the "right" partition is: multi(0)disk(0)rdisk(0)partition(2) And when the system is booted off the USB stick, this second partition becomes: multi(0)disk(0)rdisk(1)partition(2) Do read these: http://www.msfn.org/board/BOOTINI-and-diff...5.html&st=2 http://www.microsoft.com/technet/prodtechn...f.mspx?mfr=true jaclaz

Please post the boot.ini you have on the stick. (open in notepad, copy and paste) Most probably it is pointing to the "wrong" partition (the hidden one), as Ponch already pointed out: And that is one of the FAQ's: http://www.msfn.org/board/FAQs-t116766.html It is possible, depending on the contents of the hidden partition, that install starts and then errors out. jaclaz

Just for the record, an alternative could be Windowsgate: http://www.911cd.net/forums//index.php?showtopic=21204 (the 911CD forum seems down right now, use cached page temporarily): http://64.233.183.104/search?q=cache:S48Ie...p%3Ft21204.html but you can find it elsewhere: http://www.boot-land.net/forums/?showtopic=4070 http://www.boot-land.net/forums/?showtopic=4245 jaclaz

NOT an answer, but something to think about. While playing with this thingy here: http://www.boot-land.net/forums/?showtopic=3717 (which might be of interest to you anyway) I found out that the files in \System32 needed to run this Registry Viewer: http://paullee.ru/regstry Are these ones: Directory di W:\XPCL10M\Addons\rv\System32 08/01/2008 21.17 <DIR> . 08/01/2008 21.17 <DIR> .. 17/08/2001 23.36 370.688 aclayers.dll 17/08/2001 14.32 50.620 command.com 17/08/2001 14.31 27.097 country.sys 17/08/2001 14.37 53.840 dosx.exe 21/07/2001 15.40 127.213 ega.cpi 17/08/2001 14.31 4.768 himem.sys 17/08/2001 14.32 14.710 kb16.com 17/08/2001 14.31 42.537 keyboard.sys 17/08/2001 14.35 817 mscdexnt.exe 17/08/2001 14.31 27.866 ntdos.sys 17/08/2001 14.31 33.808 ntio.sys 17/08/2001 23.36 395.776 ntvdm.exe 17/08/2001 14.32 3.338 redir.exe 17/08/2001 23.36 39.936 rtutils.dll 14 File 1.193.014 byte (files are from XP SP0) So it seems like there is an entire "NT-DOS" subsystem buried inside XP, it should be the so-called NTVDM: http://support.microsoft.com/kb/314106/en-us I have made not further invstigations on this, but maybe it can be a start point for you. jaclaz

@Idontwantspam For the record, there is no need for the fixboot and fixmbr steps, just replacing NTLDR and NTDETECT.COM will be enough in the case of 2K "overinstalled" on XP. MBR and bootrecords are the same. @specialbao1 but doesn't the Win2k start normally? You can well use it to replace these two files. If not, there might be another problem, like a failed installation and what not. jaclaz

No prob. Hope you will be able to fix your build soon. jaclaz

@JayDogg As said the best example comes within the download as wainstall.bat, but you may also get this little script I wrote some time ago: http://home.graffiti.net/jaclaz:graffiti.n...ts/VDM/vdm.html and this one: http://home.graffiti.net/jaclaz:graffiti.net/ http://home.graffiti.net/jaclaz:graffiti.n...X/mbrfix0.2.zip Expecially the second one is rather straightforward and both are (well )) commented, you need a really basic batch commands knowledge to copy and paste bits and pieces and assemble your own routine. The basic "choice" menu Smiley357 posted would become using Wizapp something like this: :p :: We set the page variable to be able to return here :: after a Cancel request. set page=:p set watitle=%mytitle% set watext=%mytext%~~Please choose one of the following set watext=%watext%~Make your selection and press the [Next] button set watext=%watext%~(you can use numerical keypad) set wafile= set walistsep=; set wainput=^&0. Install;^&1. Move;^&2. Copy;^&3. QUIT PROGRAM set waoutnum= set waoutput= set wasig=%mysig% start /w wizapp NOBACK RB if errorlevel 2 goto :cancel :: no Back possible call %wabat% set choice=%waoutnum% If NOT DEFINED waoutnum goto :error IF %choice%==0 GOTO :ZERO IF %choice%==1 GOTO :ONE IF %choice%==2 GOTO :TWO IF %choice%==3 GOTO :THREE Then choices would be something like: :ZERO Start /w install.cmd GOTO :EOF :ONE move.cmd GOTO :EOF :TWO CALL copy.cmd GOTO :EOF :THREE GOTO :EOF (just examples, of course, showing different ways to invoke another batch file) jaclaz

What you describe is a bit too "vague" to pinpoint the problem, I am afraid. Can you try to better describe what's happening? I.e. try to list what you see happening until you experience the reboot. Also please post some details on the actual PC you are trying to install to, laptop/desktop, make/model, type and size of hard disk(s), how it/they are partitioned, are you truing to install from a USB stick or USB hard disk, etc. Maybe dumb recommendations , but unplug any other USB device (except mouse/keyboard) and make sure you are putting the USB stick or hard disk to one of the USB sockets on the back of the PC if desktop, (the ones soldered to motherboard, NOT the front ones connected to a cable). Do not use external USB hubs. Yes, that should make not any difference since you are well past the booting phase. jaclaz

Well, you seem to have ripped it yourself: http://en.wikipedia.org/wiki/Great_Ormond_Street_Hospital However the idea of a google shell is really nice! Thanks for the link. jaclaz

Change this: REM ---- Copy mdc file from build server ---- COPY /V %file1% %newfile% IF ERRORLEVEL 1 GOTO :ERROR to this: REM ---- Copy mdc file from build server ---- ECHO ON COPY /V %file1% %newfile% IF ERRORLEVEL 1 GOTO :ERROR and this: :ERROR COPY /V E:\CognosData\Cubes\%filename%\old\*.mdc E:\CognosData\Cubes\%filename%\temp.mdc d: cd\"program files"\cognos\c8\webapps\utilities\cubeSwap to this: :ERROR COPY /V E:\CognosData\Cubes\%filename%\old\*.mdc E:\CognosData\Cubes\%filename%\temp.mdc d: cd\"program files"\cognos\c8\webapps\utilities\cubeSwap ECHO OFF and post output when run. once again you can remove the set statements that are not used: Can you also post the actual value of the %CLASSPATH% variable at the end of all the SET statements, the command line must become ENORMOUSLY long, and that may be a cause of problems. jaclaz

Maybe, just maybe, if the drivers are "monolithic" or however, even if multiple files, do not have "cross-references" between them, you could try renaming the driver(s) and create as much as modified .inf files as needed. Say that you have a driver called videofed.sys and a videofed.inf file for it, you can try making a copy of both, then: 1) rename copy_of_videofed.sys to videofe1.sys 2) rename copy_of_videofed.inf to videofe1.inf 3) edit videofe1.inf replacing all occurencies of videofed.sys to videofe1.sys, edit also the description in [strings] section Not easy, not necessarily working, but worth a shot. An app to edit .inf files: http://www.boot-land.net/forums/?showtopic=3960 (but you can use notepad allright) Some info on .inf files: http://www.boot-land.net/forums/?showtopic=1966 jaclaz

surfetje the "HAL" error has NOTHING to do with NTDETECT.COM. This may only resolve 0x0000007b error. However to create your own modified NTDETECT.COM, if you cannot simply replicate the instructions from ilko in post #4 above: READ the linked to posts on 911CD: http://www.911cd.net/forums//index.php?sho...=19235&st=2 http://www.911cd.net/forums//index.php?sho...3784&st=334 AND the posts there referenced. jaclaz

Maybe you could have a look at this app: Wizard's Apprentice http://wizapp.sourceforge.net/ Using it and the given examples it is pretty straightforward to do what you want to do, it is also a bit nicer than a "pure" .bat or .cmd file, and will work on both 9x/Me and NT/2K/XP/2003. jaclaz

A non-hidden 12 partition becomes a visible 02 one. How is it really formatted? You might want to try the "selm" parameter. jaclaz

Almost correct . Should be: Wrong. The drivers need to be integrated to the install SOURCE, NOT installed anywhere. If the drivers are properly integrated in the source SETUPLDR.BIN (or NTDETECT.COM) will detect the need for them and install them. As said, the alternative to integrating the drivers in the source (and burn a new CD/DVD) is to manually supply the needed drivers during setup, pressing F6 and "feeding" the install with the drivers on floppy. jaclaz

I am not sure I get the meaning of your request. If during setup you do not press F6 and supply the appropriate drivers on floppy, if the Windows setup (or ntdetect.com) finds a SATA interface and drive when booting, it searches within the source \I386 whether appropriate drivers are present: 1) if they are found, it installs them 2) if they are NOT found, you'll get a BSOD error, most probably a 0x0000007b one. nlite is one of the tools able to integrate the drivers in the \I386 source, but they can be manually integrated and there are other apps, like this one: http://www.softpedia.com/get/System/Boot-M...o-Builder.shtml http://www.winfuture.de/xpisobuilder You need either the appropriate drivers on floppy and use F6 or have them intgrated in source, what do you mean by "order"? If you do not have a floppy and do not want to integrate the drivers, you may use this trick: http://www.911cd.net/forums//index.php?showtopic=20543 jaclaz

Similar thread updated with new info: Newish option, Terabyte MBR Utility can istall MBR's that allow for pressing a Fn key to select a "recovery" partition: http://www.msfn.org/board/Create-My-Own-Re....html&st=26 jaclaz

For the record, it seems like the MBR Utility (Freeware from Terabyte): http://www.terabyteunlimited.com/downloads-free-software.htm http://www.terabyteunlimited.com/downloads/mbr.zip Has, between others, an option to install a MBR using F12 (or other Fn key) to access a recovery partition and one to install a MBR using Fn key to access a recovery partition and change it's type: jaclaz