jaclaz

It is working now, as said boot-land is/was transferring to another server and changing a few policies, so a "glitch in the matrix" is very possible: http://boot-land.net/register/ just tested it, it works now. About your other questions, I suggest you NOT to change default Windows folder structure, and definitely NOT the \System32\ one, as a number of apps will look there anyway. Maybe in a second moment , when you will have got some familiarity with all the "tricks of the trade" You should use Procmon: http://technet.microsoft.com/en-us/sysinte...s/bb896645.aspx or a similar app from within the system to "trace" a boot. jaclaz

Just for the record, the Softmaker Office 2006 Free Edition can be found here: http://www.softmakeroffice.com/ jaclaz

Actually there is no "speed difference" in data transfer. http://en.wikipedia.org/wiki/Serial_ATA BUT NCQ - only available in AHCI mode: http://en.wikipedia.org/wiki/Native_Command_Queuing can make the difference in "real" speed. In other words, using a drive WITHOUT NCQ, there won't be differences, if using newish drives WITH NCQ, there will be a speed increase (and lower CPU overhead). The size of the Queue (bigger for SCSI drives) accounts also for some of the reasons why some of them are being faster than SATA. jaclaz

I didn't get you wanted to use Notepad, yes , you should use START /W "" "%SystemRoot%\system32\notepad.exe" "%systemdrive%\Drivers\MeerInfo.txt" jaclaz

Sure, life is tough.... ...whats the problem with registering on boot-land? The file is anyway bigger than the max size alllowed on MSFN. jaclaz

Sure, both original Dietmar's Registry Hives and my (integrated) ones are in XPcli_build.zip, attached to the referenced post: http://www.boot-land.net/forums/index.php?...=3717&st=47 if you just follow the posted instructions and take a bit of time reading the whole thread starting from the referenced post, where some more hints are givenyou should have no problem in buiding, either manually - but WHY? - or using the batch, a working XPCLI. I have tested it with both SP0 and SP1 and cdob reported it as working with SP2: http://www.boot-land.net/forums/index.php?...=3717&st=68 I cannot see any reason why it shouldn't with SP3 also, though AFAIK is untested. jaclaz

Should be: And then, this: Should be: (read here): http://www.ss64.com/nt/start.html http://www.ss64.com/nt/more.html but you can simplify it by simply using: jaclaz

mitsukai, don't want to put you down or anything, but since you are going the "minlogon" way, why don't you start from the already tested and working project? At least try building it, either with my "caveman" batches: http://www.boot-land.net/forums/index.php?...=3717&st=47 or with the Winbuilder project by allanf: http://www.boot-land.net/forums/index.php?...=3717&st=67 Dietmar has put a lot of effort in building the "base" hives, it seems to me just wasted time to repeat his steps to get to exactly the same result, or however, I guess you will save a lot of time by modifying the as said already working and tested "base" instead of starting from scratch. jaclaz

That's perfectly "normal". You used "/makelocalsource" switch. The switch should: 1) copy locally files to $WIN_NT$.~BT and $WIN_NT$.~LS 2) copy NTDETECT.COM and NTLDR (actually a copy of SETUPLDR.BIN renamed as NTLDR) to ROOT of Active Partition Then "nothing happens", sure nothing will happen until you re-boot, this time from the hard disk. Do check if a migrate.inf file has been created in $WIN_NT$.~BT, though. jaclaz

This may come useful, then : http://www.matcode.com/codes.htm jaclaz

In other words, being: you propose to "adjust" a "reported-as-not-working-template" Let's see if we can solve the problem. @ner HINT: try running simply @ECHO OFF SETLOCAL ENABLEEXTENSIONS SETLOCAL ENABLEDELAYEDEXPANSION REM ******************************** REM ENTER BELOW DESIRED DRIVE LETTER SET CDROMLETTER=K REM ******************************** IF EXIST ChangeCD.txt DEL ChangeCD.txt FOR /F "tokens=2,3,4" %%A IN ('ECHO List Volume ^| diskpart.exe ^| FIND "Volume" ^| FIND /v "Volume n."') DO ( Set Busy=!Busy! %%B SET Type=%%C SET Type=!Type:~-3! IF !Type!.==ROM. SET CDROMVOL=!CDROMVOL! %%A&SET CDROMCOUPLE=!CDROMCOUPLE! %%A%%B ) SET CDROMS=%CDROMVOL:~0,2% IF "%CDROMS%"=="%CDROMVOL%" ( SET NEWCDLETTER=%CDROMLETTER% SET VOLUME=%CDROMCOUPLE:~1,1% SET LETTER=%CDROMCOUPLE:~2,1% GOTO :Change_letter ) :Choose_letter FOR %%A IN (%CDROMCOUPLE%) DO ( SET COUPLE=%%A SET VOLUME=!COUPLE:~0,1! SET LETTER=!COUPLE:~1,1! IF "!LETTER!"=="%CDROMLETTER%" GOTO :Skipped ECHO Volume !VOLUME! is a CD/DVD ROM mounted as letter !LETTER!: ECHO Please enter a new drive letter for Volume !VOLUME! [Press ENTER to leave current] ECHO Already BUSY drive letters are %BUSY% SET NEWCDLETTER=!LETTER! SET /P NEWCDLETTER= IF NOT "!NEWCDLETTER!"=="!LETTER!" CALL :Change_letter ) GOTO :EOF :Change_letter FOR %%A IN (%BUSY%) DO ( REM IF "%NEWCDLETTER%"=="%CDROMLETTER%" GOTO :Skipped IF "%NEWCDLETTER%"=="%%A" CLS&ECHO Letter %NEWCDLETTER%: is BUSY. &GOTO :Choose_letter ) ( ECHO SELECT VOLUME !VOLUME! ECHO ASSIGN LETTER=!NEWCDLETTER!: )>>ChangeCD.txt :Skipped ECHO. ECHO Volume: %VOLUME% ECHO Current: %LETTER%: ECHO New: %NEWCDLETTER%: GOTO :EOF NO guarantees of it working properly, nor of it working at all, mind you. @darksimon The whole problem is that diskpart has not a way (or at least we didn't find one) to determine whether a drive is a USB one (or maybe the Vista version has? ) But you can "adapt" the above "template" for using the data in the "label" column to identify correctly a (USB) Volume with a given LABEL. Cannot say what happens if you change the actual drive letter from a batch which is running from that same drive. jaclaz

I guess you cannot format a partition unless you select it. http://support.microsoft.com/kb/928543/en-us http://www.ss64.com/nt/diskpart.html Maybe you miss lines: Or maybe you still have the first partition "in focus" when you try to create the second, and you need another "select disk 0".... Rule of the thumb whenever a script does not work is to try the commands in it one by one manually, so that you can see which one throws the error.... jaclaz

@Offler My remark was NOT intended to start yet another FAT vs. NTFS flame war, I will REPEAT, maybe bolding helps: Everyone should form his own opinion on the matter and choose whatever filesystem he feels confident with or simply "likes" better. If you want to discuss BIG FAT32 volumes, read this first: http://www.pcguide.com/ref/hdd/file/partFAT32-c.html Fragmentation is obviously more probable when the "minimum unit" (the cluster in FAT filesystems) grows in size. NTFS indexes single sectors, no matter size of volume, thus it is more efficient with bigger volumes, but has other drawbacks. jaclaz

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon or if you prefer SOFTWARE Microsoft\Windows NT\CurrentVersion\Winlogon Value "Shell" The app is still highly experimental, and the interface is a little different from usual ones. Just right click on the parent key and choose "Add". You cannot (yet ) add a new value, you can only edit existing values. jaclaz

First thing you need to understand is whether the problem is within the external drive or in the PC. Try connecting the hard disk to another PC and see if it behaves the same. If it does, the problem is likely to be in the hard disk or in the hard disk case controller, or possibly even in cables. If it does not, it is probable that the problem is a software one, with some driver (or - expecially with USB devices - some Filter driver) and can probably be fixed via uninstalling and reinstalling drivers. Check also with the Events viewer if there is any logged error. jaclaz

it's working for me (maybe ot was the Server transition that caused it to be not working): http://nunobrito.eu/download.php?view.10 http://nunobrito.eu/request.php?10 Just as a teaser , here is a screenshot with BBlean: jaclaz

There are THREE ways to "skip the R" and get directly to Recovery Console, which actually are the same, involving the change of the bootsector. You either have a hexedited bootsector, use grub4dos to hexedit it on the fly, or use NTLDR with /cmdcons switch. I don't think that anyone ever found a way to "skip the R" DIRECTLY from CD. As well, though I am NOT done with it, it seems like there is no way to use the "no more CATCH 22": http://www.911cd.net/forums//index.php?sho...20983&st=25 (which is VERY useful ) unless you use a (USB) stick or drive.... jaclaz

You cannot, as you are using NTLDR as primary loader. We need an entry in BOOT.INI to boot Windows XP, as NTLDR looks in BOOT.INI and grub4dos chainloads NTLDR. There are alternatives: 1) Install grldr.mbr to the MBR 2) put a single entry in BOOT.INI pointing to grub4dos and use in grub4dos a mapped "XP boot floppy" to actually load Windows 3) have another NTLDR renamed to something else and hexedited to look in a renamed BOOT.INI, say BOOT.INN 4) change the name of the loader in the partition bootsector to GRLDR: http://www.boot-land.net/forums/index.php?showtopic=2362 5) always boot to DOS and load grub.exe from there 6) .... 7) .... 8) .... .... Though, of course if all you have to do is dual boot between XP and 9x/Me, good ol' NTLDR and bootpart are all you need. I mean, always use a KISS approach, using grub4dos to just do the above is a bit like using a cannon to shoot at flies... jaclaz

Yep, site will be back soon. Actually the BBLEAN used in current XPCLI is BlackBox... http://bb4win.sourceforge.net/bblean/ (or at least is one of the main "branches") Which one would you like to use? ...and I would also like to change almost anything. jaclaz

Well, I have NO msn/yahoo anything. What is the problem opening a thread here or (better for this particular topic) on boot-land? You can also try using this app for OFFLINE Registry editing: http://www.boot-land.net/forums/index.php?showtopic=4684 Why don't you join the XPCLI project? The idea is starting from the LEAST possible configuration and ADD things, INSTEAD of REMOVING a bunch of things, then remove some more, then remove some more....and get to the point where cross-dependencies makes everything a mess. This way the build is "modular" and if each "item" is complete of all dependencies, each item will be "self-standing" and addable or not. jaclaz

As said, you need to actually read and understand the basioc troubleshooting steps in the given links: http://www.windowsnetworking.com/articles_tutorials/ First thing you need to have a valid TCP/IP settings, (each computer should be able to ping each other), then you need to see what protocols you enable and set them properly. Start from a SIMPLE setup. Check, if any, the router TCP/IP settings. Disable it's DHCP. Use a "narrow" SUBNET MASK, like 255.255.255.240 on ALL devices. Use a "normal" intranet set of addresses, like 192.168.0.1, 192.168.0.2, 192.168.0.3, etc. Forget for teh moment about DNS and Gateways. jaclaz

Well, you can already boot XP directly from NTLDR+BOOT.INI, thus all you need is probably an entry in menu.lst such as: title Win98 find --set-root /io.sys chainloader /io.sys (if you have more thatn one partition with IO.SYS in the root you can use a "tag" file, something like "thisis_c.tag" to "identify" the right partition. title Win98 find --set-root /thisis_c.tag chainloader /io.sys or "fix" the drive: title Win98 root (hd0,0) chainloader /io.sys But of course it all depends on tastes.... jaclaz

For the record, and probably unneeded, the "dependencies" of regedit appear to be a bit complex and I guess that most Registry editing programs use the same ones. In this seemingly unrelated thread, you will find a list of the actual dependencies: http://www.boot-land.net/forums/index.php?showtopic=3717 and an almost (but not fully) working "native" Registry Editor that needs none of them. jaclaz

I am not sure to have understood your problem. Since the posts above some progresses have been made, you may want to loook at this: http://www.boot-land.net/forums/?showtopic=5316 it may contain the solution you are seeking. Please be patient boot-land is experiencing some intermittent server problem. Otherwise, please post some more details, your setup your exact goal, etc. jaclaz

Well, only with the VISTA version of diskpart, the XP one cannot access USB drives. jaclaz