jaclaz

@submix8c But if the idea is to do a RIS install the "diskless" station must have a disk on which you install the XP after having PXE booted to the server . jaclaz

Which is "normal" , since the procedure is not called "netboot", but rather "RIS install" or "PXE boot" or "boot from LAN" (and you will find more info for this on reboot.pro, including a dedicated subforum), here: http://reboot.pro/forum/12-boot-from-lan/ jaclaz

These are "separate" issues. The BSY or LBA0 issues are the result of *something* that causes the disk firmware to enter a *loop* of some sort. The "cure" is a method/procedure to exit this *loop*. Bad sectors may develop for several reasons that have nothing to do with the above (and that cannot be fixed). The fact that you updated the firmware (which is never recommended and definitely NOT suggested in the case of flashing a Seagate firmware over a HP one ) may be part of the cause of the bad sectors, but not necessarily. That disk is now "gone for good", if it has developed bad sectors (and continues developing them). If you have on it data that you wish to recover , you should have NOT updated the firmware, and in any case now you may look for professional recovery services. If you managed to recover the data on it, it's time to throw the stupid disk in the dustbin and buy a newer one . jaclaz

Well, that's only because in all this time your paths never crossed a DELL. They are reknown "troublemakers". Happy you managed to have it working. jaclaz

Look, if you read attentively the given thread: http://reboot.pro/topic/3765-arc-path-quiz/ it is clear how the result of using a cdrom(xyz) arcpath normally results in a 0x0000007b, and usually VV2006 (and all the other posters on that thread) actually know where their towel is . If you try and explain what your actual issue/problem is (as opposed to revolving around what is the solution to it according to you) maybe it is possible that someone can help you in solving or workign around the actual problem/issue . If you want to go ahead along that path, possibly you may find of interest this thread here: http://reboot.pro/topic/12339-prepe-fast-boot-pe/ which hints about a "hybrid boot" of a PE 1.x (and the Windows XP install is a "particular" kind of PE 1.x), though still there is not (yet) a solution for booting from CD-ROM. jaclaz

And this what has to do with the ARCPATH cdrom(xyz) mapping? If you need a floppy drive for "F6 drivers", you can use a virtual floppy alright, using grub4dos and firadisk. jaclaz

Self-evident. Measurable and tested. NOT measurable, still entirely to be proved/tested. jaclaz

Point being how much you can manage to sell it, Italians do it better : https://www.tate.org.uk/art/artworks/manzoni-artists-shit-t07667/text-summary http://www.tate.org.uk/art/artworks/manzoni-artists-breath-t07589/text-summary jaclaz

Additionally there are dedicated topics to install XP from USB that actually use a .iso image mounted through either Firadisk or Winvblock either as ramdisk or filedisk here: http://www.msfn.org/board/forum/157-install-windows-from-usb/ and on RMPREPUSB site: http://www.rmprepusb.com/ 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