Cyberchicken

It's the first time that I make serious tests with OnePiece's AIO pack. I was using Ryan's and Xable's before. Also the conditions which cause the malfunctioning are a bit hidden. I'm gathering some more data (setup logfiles) and writing to OnePiece. Thank you Fabio!

It's the first time that I make serious tests with OnePiece's AIO pack. I was using Ryan's and Xable's before. Also the conditions which cause the malfunctioning are a bit hidden. I'm gathering some more data (setup logfiles) and writing to OnePiece. Thank you Fabio!

I prefer using all my software in english, traslations sucks and make debugging harder. Actually never saw the italian thread in these years; I also use google in english Do you think I *should* translate or just that I might if I want? BTW I left off many details, but just ask! I'm using the last AIO Thank you for the prompt response (and for the addons!!!) PS I scanned the entries.ini and I found no discrepancies in file name casing but I might be wrong. It could be in some other inf.

Hello everybody. I'm a bit emotional writing to you for the first time. I'm an italian guy who's been making his own XP setups since, well, almost since xp came out. I recently switched to OnePiece AIO update pack with good satisfaction, because it's very well made. But I think I found a bug, a small glitch which becomes a big pita for my way of doing things. I'm used at installing many different copies of XP on my machines (as a backup/testing/whatever). (It just needs some lines changed in the sif and creating folders with placeholder files in the $OEM$) I have two ways of installng Xp. First: from a cd (or cd image mounted in a vm) - the usual "press any key to start windows setup..." Second: from whitin a running XP I run a batch with cd i386\winnt32.exe /Dudisable /unattend:winnt.sifin a folder with the same contents of the cd (or even the cd itself, but using that command line). Well these two methods have alway been equivalent for many years (except for performance) but now they don't work the same at all any longer. Sorry for the long introduction. The big problem is that f I install XP from a folder (with the batch, no cd "press any key") Terminal Services don't get installed, and also I get "Setup cannot copy the file NetFx11.inf" during textmode file copy section. Thera may be other problems, I can't tell, but TS alone is paramount. (DotNet 1.1 doesn't get installed anyway) I think the problem is a filename casing mismatch between some inf and the files themselfes. I'm pretty sure about this because my experience: I once produced a cd with all filenames UPPERCASED and setup kept givin me this error. Turned off the option and all went back to normality. Therefore I know for sure that even if the files are correctly cased on the cd (joliet fs) the textmode part of the setup can read only the lowecased ones. To be precise textmode reads only the 8.3 filenames wich are not cased the same as the Joliet filenames. I think the other way is perfectly clear: a file is lowercased in the inf and gets read correctly when it's on the cd BECAUSE the cd driver of the textmode reports ONLY lowercased 8.3 names. BUT if the file is on a NTFS folder it gets read in a different way and setup doesn't find it. Yes, we all now that Windows filename casing is not sensitive in general, but I'm talking of just the textmode of the setup. Please please please pretty please, could you put an eye into it? Telling me that I'm not crazy would be great, but fixing this would be great and VERY MUCH appreciated PS I do my Xp setups with Nlite and VirtualBox among other things.My conclusion about the cd / folder question is not a matter of guessing: I've been able to reproduce it right now both in a vm and in physical.I'm ready to make any test you want, and to translate all this stuff in Italian if needed.I never learnt how to make addons myself but I'm going to check myself if I can find any proof of the case mismatch. With hope Thank yoy