jaclaz

Slightly OT, but you can try the "Universal VESA/VBE video driver", here: http://www.boot-land.net/forums/Universal-...driver-f60.html (and given links) Just a few minutes ago a member reported success with it in winbuilder, but it should work alright in full windows as well, at least you can have a higher resolution until someone finds the problem with the install of "full" driver . jaclaz

I am not at all an expert on this, but my guess would be that a year 2005 post can hardly refer to WinPE 2.0, which has been released in late 2006/beginning of 2007. Unless the original poster had a VERY GOOD crystal ball, that post must reference to WinPE 1.x, XP based, NO .wim whatsoever.... jaclaz

Also please note that: I the appropriate context, "many" means not "all" nor "most", rather "a certain number" and there might be several added steps, specific to each application to be performed before making it work, often only partially. So, rather than triyng to find a one-size-fits-all solution (that does not exist as far as I know), you'll probably have a higher success rate searching on the board for the specific application, and only if you cannot find anything try the methods suggested, knowing that if they don0t work it is possible that some other "tricks" might be needed before giving up. jaclaz

There is NO difference in booting with a NTFS formatted drive. Problem might be that some motherboard's BIOS do not allow it. Of course if using a Flash drive, NTFS is NOT suggested due to wear problems. This, the 911CD and boot-land.net boards are FULL of threads detailing different procedures to boot from USB, if you can be more specific on what you want to do, I can give you some links and possibly help you in the procedure. The most straightforward way is to use grub4dos grldr as an entry in your BOOT.INI, but there are other methods too. jaclaz

Version 1.4 is out. jaclaz

No, I can confirm you are not the first one, that is what the Winbuilder project is being developed for, I am not sure about Firefox, but there are working scripts for both OPERA and the very minimal Offbyone. jaclaz

lol, i dont even use my laptop on top of my lap. and what if u call it a notebook? you dont take notes in it and its not a book.. A word of WARNING: DO NOT EVER try to swallow a "Tablet PC" :rofl: jaclaz

src2206, with all due respect, my guess is that your falling in the basic error of newbies, i.e. wanting to do everything at once and in one step. Unfortunately, most probably this way it won't work. You should try making things one at a time, though a slower process, it is the only one that allows for easier troubleshooting and, ultimately, for success. Specifically, an unattended CD is, well , UNATTENDED , there is NO WAY you can perform a Repair with an UNATTENDED CD, one fuction excludes the other, unless you make an UNATTENDED REPAIR CD, which you can ONLY use as Repair CD, pretty much useless to have .NET silently install with it.... I NEVER found anyone being able to create a fully working UNATTENDED CD in the first, say, less than 5 attempts, and only after a great number of tests in VM's. Another thing is a PARTIALLY unattended CD, i.e. one where only some of the more "boring" things, like Serial number, Computer Name and Network, etc. are pre-set, but even this is not as easy to do as it might seem. What you need is a "normal" NON-unattended slipstreamed CD, and (maybe later) another CD that can be UNATTENDED. About .NET unattended install, start here: http://www.msfn.org/board/Add_NET_framewor...tal_t60638.html jaclaz

Was there a doubt it wouldn't work? No prob, mate. jaclaz

Hmmm, I guess it should be the other way round. I mean, a "valid" SHELL= statement in config.sys, should have the full path to the shell, like in: or since COMMAND.COM is one of the three boot files, together with MSDOS.SYS and IO.SYS, it should reside on the root of the boot disk, and, on the other hand, CONFIG.SYS should also be there, so: should work as well, as long as the CONFIG.SYS that has that line is on the same (root) directory of the booted drive, if COMMAND.COM is anywhere else, a FULL path or an updated %PATH% variable is needed. The "strange" fact is that the presence of AUTOEXEC.BAT with length >0 changes, from what you report as second example, the behaviour, in the case COMMAND.COM is on the root directory, just as if the mere presence of AUTOEXEC.BAT would make it "root" to it correctly. So, if I get what you report correctly, it seems like in one case the "root" is (as it should) C:, whilst in the second is somehow "undefined". Since we are talking about DOS7.1 here, could the above be somehow connected with changes (if any) in the contents of the MSDOS.SYS file? http://www.computerhope.com/msdossys.htm jaclaz

The problem might be the NUMBER and DIMENSION of ranges you need to compare to. If I am not mistaken, IF statement allows a max of 7 levels of nesting, so, for two ranges (up to seven) you can do something like (in cell I3): =IF(F3-10<0,0,IF(F3-20<0,1,"Out of Range")) for three ranges: =IF(F3-10<0,0,IF(F3-20<0,1,IF(F3-30<0,2,"Out of Range"))) and so on... Another way could be to parse the number: =IF(LEN(TEXT(F3,0))>1,left(TEXT(F3,0),1),0) The above will work for TEN ranges 0÷9 to 90÷99 A better approach could be to "dynamically" find the length to be parsed: =IF(LEN(TEXT(F3,0))>1,left(TEXT(F3,0),LEN(TEXT(F3,0))-1),0) The above will work for all ranges as long as they are in 10 "steps" Otherwise you will need to build a table like this say in colums M and N (in the example with 5000 "pairs"): 0 0 1 0 2 0 .... 10 1 11 1 .... 325 This can be anything 326 This can be anything ... 4217 A suffusion of yellow 4218 A suffusion of yellow then use: =VLOOKUP(F3,M1:N5000,2,False) The table can also be built on another sheet, of course. Please take note of the last parameter of the above formula, if it is 0 or False, it will search for an EXACT match, thus you will need to build a table with ALL possible values, but if it is 1 or True, it will get the nearest value it can find LESSER than the searched one, thus you can build a table with just the starting figure of each range. For the latter to work, the table MUST be ordered with increasing values. jaclaz

Just for the record, the proper way to check for a directory should be checking for nul.ext instead of nul, at least on NT based systems, reference: http://xset.tripod.com/tip5.htm http://msmvps.com/blogs/martinzugec/archiv...-same-name.aspx It is a remote possibility that there exists a file with same name as folder, but you never know. jaclaz

Yes, "Commercial" programs should all have such a provision. Since, to be accurate, you do not actually need an image, but rather you only need to clone the disk, this Freeware one could be just right for your scope: http://www.miray.de/products/sat.hdclone.html#free http://www.miray.de/download/sat.hdclone.html The FREEWARE version is slower than the Commercial ones, of course, but since noone is chasing you, it might be worth at least a try, on the other hand, as it offers less options, it might be easier for a novice. I think it will only expand the OLD "small" partition to a "bigger" one, but I guess it will be allright, there are other programs to resize/create expand partitions, that you can use later. With reference to my previous post: Since your new HD is SATA and most probably you do not have a SATA interface on the old machine, the above won't be possible, you'll need to do something different: 1) Burn a bootable CD from the downloaded HDclone file, TEST it on BOTH the new and old PC to make sure it boots properly, do also test the "nlited" INSTALL CD, ideally you should try to install XP from THAT CD on the NEW machine (and later format the drive) to make sure that everything works as expected 2) "Prepare" the OLD IDE HD on the OLD machine by removing all devices from Device Manager, IMPORTANT do some preventive tries with just removing, say, the video card or PCI IDE driver and see if at next reboot it is redetected correctly, it is ESSENTIAL to be able to revert back if something goes wrong (one OLD working PC is still better than one non-working NEW one and definitely better than having two computers BOTH non-working). As soon as you are sure that the removal and re-detecting works (it is OK of a "standard" driver is re-loaded instead of the "specific" one, do the complete removal. Do read this (Win2k, but most can be applied to XP too): http://www.motherboard.windowsreinstall.com/win2k.htm with particular attention to solution #4 and #6 3) Shutdown the OLD PC and DO NOT RE-BOOT IT, take the IDE HD out of it. 4) Go to the new PC and MAKE SURE that in the BIOS boot order is setup so that CD boots first, if possible disable booting from ANY HD alltogether 5) Try once again booting from CD to make sure 6) Shutdown new PC and install on it the OLD HD 7) Boot from the HDclone CD and perform the cloning 8) Once cloning is over, remove HDclone CD, shutdown the PC and remove the old HD 9) Power ON PC, go in the BIOS and set it to boot from CD first then HD, insert the "nlited" CD (WITH the SATA drivers for the new PC or be ready with a floppy with the "F6" drivers) 10) Boot from it and do the Repair as in: http://www.michaelstevenstech.com/XPrepairinstall.htm 11) you might need to go through a series of re-boots, with a bit of luck, everything should work The procedure above has the advantage that should anything go wrong, your OLD hard disk has got no modifications of any kind, so it will work if put back on the OLD machine, and you can start anew, maybe with a different software/procedure. NEVER, and when I say NEVER, I mean NEVER allow the new machine to boot XP from HD when BOTH hard disks are connected to it. If anything is not clear, do post your perplexities before starting the cloning. A final advice: take your time, possibly during a weekend, tell friends and relatives you are somewhere else, switch off your telephone, if possible have an alternate machine connected to the internet to be able to google your way or ask for help. jaclaz

For PE (Windows XP/2003 based) systems, probably your best bet is Native_ex/PicoXP, Winbuilder projects, here: http://www.boot-land.net/ For "Full XP" it is nlite. For Linux, it is difficult to say, as there so many distributions, my preference lately goes to Debian derivatives, like Knoppix or one of the derivatives from Knoppix, there are large communnities of "Knoppix modders", but I guess that it is just my personal opinion. jaclaz

Yes, problem is, it is not yet clear to me what you want to do. I mean, nlite can help you make a good, up-to-date, slipstreamed, possibly partially unattended INSTALL CD. It will not, in any way help you to TRANSFER your actual system to the new machine. In other words, nlite is "feeded" with Microsoft Windows XP INSTALL files, being them from original CD, from a \I386 directiry on your HD, or from Service Packs and Updates, plus it can integrate Third Party INSTALL files (for example drivers), though quite obviously it is a rather unuseful waste of space on the CD to integrate drivers specific to ONE machine if the intended use of the CD is installing on ANOTHER machine, unless the two are identical. You should get all the drivers for the NEW machine and integrate them in the nlite slipstreamed CD. But again, on the CD built with nlite there will be not the following (currently on the HD): 1) Data 2) Installed applications 3) Settings, including Network names, tcp/ip addresses, 4) Users, Passwords, ACLs, Disk quotas and more generally everything that has or needs to be set or changed after the initial installation of XP (this can be partially covered by using unattended features, but they are a bit tricky, and definitely NOT suggested as a "first try") That is why the idea of imaging has been suggested, though, as said it is not an easy and straightforward task, and needs ANYWAY a good known-to-be-working slipstreamed CD, which nlite can help you make, to be able to perform the Repair. In a nutshell, to try the TRANSFER you will need BOTH: a. A slipstreamed (with nlite or other program) Install CD b. An imaging program If you want to re-INSTALL, you need just point a. above. jaclaz

Yep, the "Thumb Drive" really cracks me up.... I wish I had one of those. jaclaz

With all due respect, 460 Mb appears to me more like "Light Heavyweight" than "VeryLight" (I presume you are talking about the OS, without, say, Office, IE7, Photoshop or whatever big-sized application. Speaking of Win2K, I would put "Extremely light" below 100 Mb, "Very Light" between 100 and 200, "Light" between 200 and 300, "Middleweight" between 300 and 400, "Light Heavyweight" between 400 and 500, and "Heavyweight" for anything bigger. If I recall correctly, an "untouched" install of Win2K is about 600 Mb. jaclaz

@ripken204 If you click on the links on my original post, you might be able to understand the idea behind it. jaclaz

Hmmm, "Usb flash drive" appears to be the most "correct" one, but there are of course exceptions, I guess these: Pen Drive USB key Thumb Drive USB Stick can be called differently with no risk of misunderstandings. jaclaz

Just out of curiosity, what tool did you use to open the plastic case, a sledgehammer? That is very interesting because there is a precedent in a famous Italian trial where the original CD containing the recordings of a supposed case of corruption (all copies proved to have been tampered with, and thus unacceptable as proof by the judge) was said to have been broken by a witness because: Now, a local Radio for about one year made a contest with a prize of something like US$ 5,000.00 for whoever would have been able to break a CD by letting it fall and catching it between his/her legs. The prize was never awarded as noone was ever able to repeat the alleged performance. jaclaz

Hmmm, the "traditional" way to try to avoid the Repair was to change the IDE bus drivers with the default MS ones "Standard Dual Channel PCI IDE Controller", and the Video to "Standard VGA", both of which are however suggested, but since you are going to have a SATA drive, my guess is that a Repair will be necessary anyway. Pardon me, but it is not very clear to me what do you mean by: Can you elaborate on the method you are planning? jaclaz

@ElTorqiro Nice find! Though when Nuhi will have tested and integrated your idea in nlite your program might prove to be mostly unneeded, if I may, I would suggest to NOT "abandon it, but rather enhance it. What if some features are added to it, something like: 1) Backup sfcfiles.dll to sfcfiles%date%%time%.old 2) Make a list of files from current sfcfiles.dll dynamically (i.e. without having an hardcoded set of files linked to a certain version of scfiles.dll) 3) Let the user choose from the list (maybe with a multi-page/multi-selection) which files he wants WFP disabled for 4) have an option to restore a previously backed up sfcfiles%date%%time%.old to sfcfiles.dll This way even the n00b could use the app in a relatively safe manner.... Cheers, jaclaz

hmmm, what ATTRIButes has that file? ATTRIB "%SYSTEMDRIVE%\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\StartVista.lnk" Maybe is hidden / system ... Besides, del /f /a /q the /a parameters, at least in 2K/XP needs the correct attribute following, like in /a:HSR the /q switch is unneeded the /f forces the deletion of a read only file, but only if it is not hidden As a general "rule of thumb" when writing batches, make them in a manner that they can be run from an open command prompt so that you have visual feedback, add to them as much PAUSE statements as you see fit to parse the output, if needed put some @Echo on and @Echo off just before and after relevant lines, to be able to check if the batch works properly, when using parameters in commands, always try with no parameters or just one at the time, double check sintax and make sure to have understood it before using parameters. A good site with help for the various commands is this one: http://www.ss64.com/nt/ Always check this site: http://www.robvanderwoude.com/ to learn more about sintax and to see examples of well written batches. jaclaz

@buseeliu Good find! It's good to have more eyes checking, typos are so easy to go undetected. See you soon ilko_t, be well. jaclaz

Hmmm, I cannot guarantee they will be "welcome" , but rest assured we will try our best to reply them . jaclaz