jaclaz

The cdrom(xyz) references (for what can be of use): http://reboot.pro/topic/3765-arc-path-quiz/ http://reboot.pro/topic/3795-testers-needed/ According to the above: cdrom(224) should be Primary Channelcdrom(239) should be Secondary Channelbut the results are not definite (nor seemingly useful). jaclaz

Well, with all due respect for the nice kid : it has to be said how the flaw: is actually a flaw that even a 5 year old boy could find. I mean, what do the good guys at MS that designed that login mechanism have inside their skulls? Popcorn, polystyrene foam or just vacuum? jaclaz

Ah well, if you say so, it's OK . Anyone reading the thread: http://www.msfn.org/board/topic/171435-allow-lowercase-on-multiboot-dvd/ will be able to form his/her own opinion on this. OT, and JFYI, datshun9.cmd : http://www.911cd.net/forums//index.php?showtopic=25612&hl= jaclaz

Quoque tu, Trip?! That sounds a lot *like* (but of course with the exteremely vague references/information you provided is just a guess) a DDP2.0 master. Like: http://www.hellmanproduction.com/dvd-authoring/how-to-create-ddp20-master-with-dvd-studio-pro.html http://www.ehow.com/how_7252367_do-ddp-file-dvd-video_.html jaclaz

AFAIK/AFAICR the three files: WIN51WIN51ICWIN51IC.SP2are OK for a SP2 "Home" install disc (and no other tag file is needed normally). I won't tell you again (but I am actually telling you this ) how most probably you did too many steps (n-liting/integrating/whatever) all together, and thus it is IMHO very possible that something created a conflict in the build (not in your system being "incompatible"). jaclaz

Allow me to doubt that that screenshot is the result of running the batch you posted, unless you have a *somehow* non-standard command processor. Try running this batch: @ECHO OFFECHO The following line is OK:ECHO "This line contains an ampersand & inside double quotes and is ECHOed fine"ECHO.ECHO The following line is OK:ECHO This line contains an ampersand ^& since it is escaped is ECHOed fineECHO.ECHO The following one it is NOT:ECHO This line contains an ampersand & will produce an error when ECHOedYou should get a result similar to this (your error message will be in German instead of Italian): I don't think there are differences when it comes to the "&" character in cmd.exe vs. command. com. With a "long" url containing an ampersand you are hitting 2 (two) different limits. One is the length limit (and this is independent from the special characters). One is the "special characters. jaclaz

Yep , what I was asking was a bit beyond that. I mean, what are the actual "patches" (to the Registry or to the files) that that choice produces? It is possible that *somehow* that particular setting/tweak is not compatible (or not entirely compatible) with your SP level (or other integrated hotfixes, etc.). Yes, this is normal, those tag files are what tells the setup to which Service Pack level is the source, see: http://www.911cd.net/forums//index.php?showtopic=16381&hl= but if you have the "IC" (and not the "IP" files) it means that your source is "Home" (and not "Professional"). What are the actual tag files you have on your source? What are the actual tag files you have on your self-made integrated disk? What are the actual tag file names in the files in your source (unmodified)? What are the actual tag file names in the files in your build (after having been processed by nite)? Since you are into iso-experiments, why don't you give to the n-lited build CD the same name as the original? i.e. instead of -volid "XP-SP2 -DE_Silent" use -volid "VRMHFPP_DE" (or whatever) see also: http://www.tacktech.com/Software.cfm?sc=windowsxp scroll down until you find the suitable: Known Windows XP .... jaclaz

And how did you disable WFP, before? jaclaz

That could mean that the "old machine" install had SATA drivers but that they are not compatible with the "new" machine, You can "force" the "Standard IDE" drivers on the OFFLINE install with DriverInjectionGUI or MSSTMAKE: http://www.911cd.net/forums//index.php?&showforum=43 and then boot (most likely only in Safe Mode intiially, as there will be probably other "different drivers") in IDE mode, then "fix" the XP install. (or try forcing "directly" the appropriate SATA drivers, though this in some cases does not work properly). jaclaz

@Charlotte I believe you are reading this: the "wrong" way (actually it is written the "wrong" way). IMHO it should have been: Layman example: Of course as soon as the third party thingy became avaialable everyone was able to change the battery at home. BTW the cited sentence is also not technically accurate, as there is not really need of a "component driver", a tool can be alright a parser for a filesystem or filesystem image, without having (and not being) any "component driver". jaclaz

Yep , but I doubt that "plain" filesystem journaling represents an effective "safety measure" (when such a number of programs and services run in the background). Having a transactional filesystem may possibly help (due to the "atomic" nature of the transaction log) and not-so-casually transactional NTFS was introduced with Vista But (just for the record), at application level, the thingy was rather poorly implemented, or documented, or both , to the point that it is now "deprecated" : http://msdn.microsoft.com/en-us/library/windows/desktop/hh802690(v=vs.85).aspx The good MS guys, however seemingly "invented" a transactional exFAT for Windows Ce/Phone, TexFAT (of which exist seemingly also a 2.x version, completely UNdocumented) see: http://www.forensicfocus.com/Forums/viewtopic/t=11393/ http://www.forensicfocus.com/Forums/viewtopic/p=6571453/#6571453 That filesystem may be (if ever it will be available/usable on "real" Windows PC's) a good "no permission/no unneeded fluff" kind of solution. But of course this - even if it will ever happen - won't change in any way the situation of the Registry which is in itself a filesystem (and actually very similar to NTFS) if you look at it from the right angle : http://reboot.pro/topic/7681-the-registry-as-a-filesystem/ A nice experiment (if anyone has time/will) would be to try making a Windows 7 "standard" install (the one with the 100 Mb stupid "boot" partition - which the good MS guys call "system" - and a second "system" partition - the one which the good MS guys call "boot"). Then replace the second partition with a "copy of it" but formatted with a UDF (or exFAT or TexFAT) filesystem. Will it work? (i.e. has the BOOTMGR the capability to access UDF (or exFAT or TexFAT) filesystems?) jaclaz P.S:: IN the mentioned thread on reboot.pro: http://reboot.pro/topic/19643-winsxs-hardlinked-files/ another member posted his experience with manifest files that can be removed from the WinSXS directory safely, so even 7 is possible. If you want to do do the test, remember that the 7 installation footprint on disk will grow to 9 Gb or more, almost 10 Gb if I recall correctly.

In Italian (Tuscany) there is a (not particularly polite ) saying used in these cases that goes like: [italian] ... e se il mi nonno aveva tre palle era un flipper [/italian] that would be roughly in English: ... and if my grandpa had three balls he was a pinball jaclaz

For NO apparent reason http://reboot.pro/topic/19683-boot-bitdefender-rescue-iso-from-usb-mystery/?p=183147 jaclaz

Grub4dos supports UTF-8 encoding alright, that allows to have all the special characters, you may need to load a special font with the font command, see: http://reboot.pro/topic/19076-grub4dos-menu-font-type/ http://rmprepusb.blogspot.co.uk/2013/11/defining-fonts-in-grub4dos.html http://www.rmprepusb.com/tutorials/grub4dos/fonts-and-graphics Also, you may want to create a "German keyboard layout" for grub4dos. , some hints and a basic worksheet are here: http://reboot.pro/topic/8056-keyboard-layout/ http://reboot.pro/topic/8056-keyboard-layout/?p=68522 The link to the (partial) german layout is dead, but can be retrieved form the Wayback Machine: https://web.archive.org/web/20090702065631/http://www.lrz-muenchen.de/~bernhard/grub.html https://web.archive.org/web/20081206092135/http://www.lrz-muenchen.de/~bernhard/german.txt jaclaz

... and we like it . jaclaz

On other news, besides the re-known Dual Elliptic Curve issue, it seems like http://www.reuters.com/article/2014/03/31/us-usa-security-nsa-rsa-idUSBREA2U0TY20140331 the "Extended Random" extension to it is an added insecurity. http://dualec.org/ jaclaz

The usual "corporate" approach is usually different. Typically a bunch of identical machines are bought, say a lot of 20 or more, the IT installs and configures one of them "properly", tests it, then images it and deploys the image to all the other identical ones. I personally count as: One, two, three, many If the number is within 3, manual installation three times is at the end of the day faster than *anything* scripted/custom, etc. If the number belongs to "many", then usually an "imaging/deploying" approach/solution is IMHO the best choice. jaclaz

Sure, there is no problem in running XP in FAT32, Vista is possible, Windows 7 seemingly no, and not really because of the hardlinks, symlinks and junctions (though of course the size grows), but because of the stupid WinSXS, and the senselessly long stupid filenames: http://reboot.pro/topic/19643-winsxs-hardlinked-files/?p=182961 (the good news being that a Windows 7 on NTFS can be shrinked by hardlinking more stuff): http://reboot.pro/topic/19643-winsxs-hardlinked-files/ jaclaz

Come on : http://www.student.tugraz.at/thomas.plank/index.html get the needed Cygwin1.dll that is a separate download: http://www.student.tugraz.at/thomas.plank/cygwin1.dll_1.7.28_.zip and if needed the Zusätzliche DLLs http://www.student.tugraz.at/thomas.plank/dlls.zip Probably it forces to uppercase in the ISO9660 "namespace", not in the Joliet one, I believe. jaclaz

Well, just for the record, the good DELL guys managed to alter permissions even BEFORE installing the XP : http://www.911cd.net/forums//index.php?showtopic=15138&st=29 they IMHO deserve the first prize . jaclaz

Iso level 3 - if I recall correctly - does not change in itself the "base" requirement of files needing to be uppercase. The joliet extension should provide support for longer filenames and for "mixed case". Iso level 4 does not really exist, it is a form of iso level 2 or 3 with some restrictions removed. The -allow-lowercase is a violation of ISO9660: http://cdrecord.berlios.de/private/man/cdrecord/mkisofs.8.html i.e. if the -allow-lowercase switch is NOT used, then any non-conforming filename (in iso-level up to 3) will be uppercased to conform to ISO9660. So, your cdrom.sy_ will become CDROM.SY_ (and txtsetup will find it), or if you had cdrom.sys it will become CDROM.SYS (and txtsetup will still find it). The downside is that the gfx-boot.gfx or GFX-BOOT.GFX may become GFX_BOOT.GFX. A "Windows XP install CD" (original) has ALL FILES CAPITAL and txtsetup wants to have them like that (at least for the files used in it, it is very possible that after txtsetup the files used in the GUI part of setup can be in *any* case, as they are accessed by the "standard" windows which is case insensitive). In a "pure" install Cd you simply don't use "-allow-lowercase" and everything is fine. Grub4dos is historically hardcoded to find a /menu.lst (or /boot/grub/menu.lst or /grub/menu.lst) and until recently you needed to (as explained early) change in the the embedded menu.lst the string "menu.lst" to "MENU.LST" (and grub to GRUB and boot to BOOT, if you used the subdirectories). Recently (but as said cannot really remember when) it was patched in such a way that the menu is found anyway, but cannot say if it accesses "generically" the file-system as CaSe InSeNsItIvE now, traditionally it needed (and used only) the Rockridge extension, which is case sensitive, recent version may access either the ISO9660 or the Joliet names. A PE 2.x (or later) has normally a "boot" subdirectory (where the boot.sdi is), though cannot say if making it "BOOT" will change anything, a Linux may need a given file in lowercase (or in uppercase or MiXed MoDe/whatever). Any of the other things that you added to your DVD (and that you won't talk about ) may have one requisite or the other, some mkisofs parameter that "fixes" one thing may "create an issue" with something else, this is the dificult part when making "multi" CD/DVD's. The traditional way for me has been that of using -iso-level 4 and adding a Rockridge extension, and NOT add the "-allow-lowercase" i.e. this set of commands : http://reboot.pro/topic/9696-oscdimg-and-grub4dos/page-2#entry84348 and that I believe correspond to your 4.2 attempt (but I have ALL FILES UPPERCASE in the source directory on hard disk from which I build, and the above post does contain a reference on why this is done - that is year 2004, ten years ago). If you insist on having the files on the hard disk in lowercase because n-lite or some other program tweak made them like that, and you don't want to change them, you will have to use a "lower" -iso-level than 4 and NOT use with -iso-level 2 or 3 the "-allow-lowercase", and find workarounds for the issues that this choice may cause. The example with GFX-BOOT.GFX vs. GFX_BOOT.GFX represents one of such issues that is easily fixable, it is to be seen what other "needs", such as the "Umlauts" may require in the mkisofs parameters. jaclaz

Well, TXTsetup expects an uppercase CDROM.SY_/CDROM.SYS, so if you are not going to uppercase it in the source, you cannot have -allow-lowercase in the mkisofs.exe (which may cause other issues, like the dash/underscore one). jaclaz

Between your test 4.7 and 4.8 you changed TWO things at the same time: Bugfix-Version 4.7: ISO-Level 3, Joliet, RockRidge, NO relaxed-filenames, allow-lowercase, Bugfix Version 4.8: ISO Level 3, Joliet, NO RockRidge, NO relaxed-filenames, NO allow-lowercase Windows setup (SETUPLDR.BIN, etc,) or more generally "windows" knows nothing about Rockridge, but the setup is sensible to uppercase/lowercase, i.e. if you try with RockRidge enabled but with NO allow-lowercase you should have the same result as 4.8, implying that there are one or more files involved in the setup that are *somehow* in lowercase (whilst they should be in uppercase). If you do (from windows command prompt) a (let's say that your CD/DVD drive - real or virtual - is drive letter E: ): DIR E:\ /s /b> C:\my47dir.txton the 4.7 test and: DIR E:\ /s /b>C:\my48dir.txtwith the 4.8 one you should be able to find the differences comparing the two files As a further test you could - to make sure - uppercase everything related to the Windows setup on hard disk before creating the .iso, as cdob just re-suggested and re-enable the allow-lowercase. jaclaz

Good , but there are n versions of 0.4.5c, by EXACT version I was meaning EXACT, like 0.4.5c-2014-01-17 (right now latest 0.4.5c) or 0.4.5c-2013-03-03 (right now "featured" 0.4.5c). One or the other version won't change the behaviour with "classic" commands (like color) but may behave differently regarding behaviour when loading (like finding /menu.lst vs. /MENU.LST and similar, cannot remember when that changed). jaclaz

Which exact version of grub4dos are you using? At the command prompt issue: help colorand check the symbolic names listed:http://diddy.boot-land.net/grub4dos/files/menu.htm#display "gray" is not a colour light-gray and dark-gray are.http://www.rmprepusb.com/tutorials/grub4dos#TOC-Grub4dos-color-values There may be a typo in the actual output of "help color": http://diddy.boot-land.net/grub4dos/files/commands.htm#color where "light-gray" is spelled (or spelt) as "light-grey". OT , shades of gray (or grey): http://reboot.pro/topic/15878-world-is-not-black-and-white/ jaclaz