UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files

johngalt · 24 Jan 2017

Could be the variables are unusable?

slicendice · 24 Jan 2017

Nope, completely non-reserved variables, they just become empty in version 1, go figure...

johngalt · 24 Jan 2017

slicendice said:

Nope, completely non-reserved variables, they just become empty in version 1, go figure...

That is odd.

Kari · 24 Jan 2017

slicendice said:

I HATE PS!!!

It does not wanna co-operate with me. I write a function 2 times with different variable names but overall the functions are exactly the same, the first version does nothing, the second works great!

WTF!?!?

Care to explain? Which variables are you trying to use? PS command you use to create it / them?

slicendice · 24 Jan 2017

This does not work:

$filesA =Get-ChildItem c:\tempA\
foreach ($fileA in $filesA){$fileA.Lenght}

This works:

$filesB =Get-ChildItem c:\tempB\
foreach ($fileB in $filesB){$fileB.Lenght}

No difference what so ever, and one works while the other does not.

EDIT: Just to clarify, it does not matter if I change the directory path, still the same issue

slicendice · 24 Jan 2017

This is why I stick to C and Assembler when I code. At least they work.

slicendice · 24 Jan 2017

In the above example using $fileA.Name instead of $fileA.Lenght works. What on earth is Windows doing with my variables/objects?

johngalt · 24 Jan 2017

slicendice said:

This does not work:

$filesA =Get-ChildItem c:\tempA\
foreach ($fileA in $filesA){$fileA.Lenght}

This works:

$filesB =Get-ChildItem c:\tempB\
foreach ($fileB in $filesB){$fileB.Lenght}

No difference what so ever, and one works while the other does not.

EDIT: Just to clarify, it does not matter if I change the directory path, still the same issue

You misspelled length in the first one.

slicendice · 24 Jan 2017

Thanks, must be that then I will give it one more try, then I give up for today.

EDIT: LOL! That's it! THANKS A TON!

johngalt · 24 Jan 2017

slicendice said:

Thanks, must be that then I will give it one more try, then I give up for today.

EDIT: LOL! That's it! THANKS A TON!

You're welcome. I learned a long time ago that a second set of eyes on code is always a beneficial thing. A second set of eyes on any written word in general, in fact.