www.sarducd.it

[davidecosta]

I don't delete thread without SPAM.
I get dozens of alerts a day, 99% are errors or problem of users.

I can tell you my experience: When something does not work I always start from the assumption that I'm wrong, I make test with more USB and with more PC. Users start of the assumption that they don't wrong.

• More time i've solved formatting the USB with RmPrepUSB
• More time I've solved with one scandisk of partition when I use SARDU.

[RighteousNewt]

I have ran diagnostics on the system. Completely checking the hardware on that system. Everything checked out fine. I also ran a chkdsk to repair the ntfs partition on the system, and sfc to repair windows.

So I tried the 32gb USB drive on the second PC. I had the exact same problem. So it is a problem with the 32GB Drive.

I bought another 32GB Drive used sardu on the original system, and it worked fine.

Thank you for your patience. I know that it was starting wear out.

[UFdFan]

@ RighteousNewt

THanks for your very good test reports.

You can tell us the hardware (usb 32GB) whatthat do not fine run?
I use only trancend USB and i have no problems.

[RighteousNewt]

@ UFdFan

Sorry about the delayed post.

USB Dive Info:

Sandisk Cruzer Glide 32GB USB Flash Drive

Model # sdcz60-o32g
Serial Provided by Sardu 2.0.6.1: 9546-7e5e

I have tried another with the exact same model # and it worked fine, but I do agree with you though. One bad apple spoils the hole bushel.

[davidecosta]

I have tried another with the exact same model # and it worked fine, but I do agree with you though. One bad apple spoils the hole bushel.

Do you truied to format them with RmPrepUsb?

[RighteousNewt]

I have used RmPrepUsb on both usb drives with matching model #'s. When I used the testing feature of RmPrepUsb the original usb drive. I noticed that it had a high latency, and that's what made me decide to buy the second drive. I didn't experience the high latency on the second drive, and everything went through just like I was expecting.

On the second drive all other versions of the windows installers work except windows 7 64 bit, but I will not post anything on it until I do some more testing.

Its specifically about bootsect.exe 64 bit from Windows 7 not extracting on windows 32 bit or 64 bit. I had thought about replacing bootsect.exe 64 Bit with bootsect.exe 32 bit from Windows 7, but I am unsure whether this would cause problems with the test iso. I am also unsure whether it would cause problems later with the windows installation.

Like I said, earlier I will not post anything on this specific issue with Windows 7 64 bit. Until I have thoroughly tested everything, or I hit brick wall.

I will also test it with sardu 2.0.6.2.

Thanks for the update davidecosta

[davidecosta]

If you think that the error is bootsect...i have planned this , menu USB --> Fix Bootsect corrupted

[circaal]

Ok first off Sardu is an amazing piece of software, But I was dealing with issues of Windows 7 as I modified my DVD but it was over the 4gb mark making it fail when trying to extract. SO what I did was decompress my ISO using winrar. Then I found the install.wim file and moved it out of the compressed iso and put it in another folder. Then I recompiled the remaining files into a new ISO making it around 600mb. Then I used Sardu and let it do it's magic. After the process was done I simply grabbed the install.wim file and copy and pasted it into the USB under source7 where it should be. So I believe this will solve the issue the same as Windows 8 if the install.wim file is the same file it uses. Hopefully this helps some people.
-BTY

[davidecosta]

No, it's wrong

Barrosu and multi installer works fine only with FAT 32. This is due to the fact that it can not write to NTFS.
The limit of one file in one support FAT32 is 4 gb

SARDU don't extract install.wim if is largest 4 gb not becouse SARDU is stupid but becouse this USB made with this file don't works fine.

[circaal]

Look I never said the program is stupid. I really do love the piece of software. I was just giving an workaround for people using a modified Version of Windows 7 or workaround for Windows 8 granted it still installs from a install.wim file.

I am running into one problem though. When I pop in the flash drive and boot from it, the setup gets to the part where you choose a disk to install it to. So I go ahead and delete any partitons on the disk at the time and when I try to install I get this error: "Setup was unable to create a new system partition or locate an existing system partition. See the setup log files for more information" I have tried everything I can think of and I even did DISKPART and clean and I can't seem to get it to install. I was wondering if anyone else was getting and issue with this. I don't know if its the ISO I'm using or if its the linux bootloader that is installed. I have install this same version of Windows 7 on a DVD and as a lone installation on a USB with no problems yet. Does anyone else have any info on this issue? Thanks
-BTY