sevnz.exe error says there's no \Device\HardDisk\DR1 in Windows Vista/Windows 7 systems

Bug #920576 reported by Joshua Shelton on 2012-01-23
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
UNetbootin
Undecided
Unassigned

Bug Description

I'm using unetbooten to extract a WinPE iso to USB.

The USB drive is quick formatted NTFS before the extraction. Right when the extraction begins, this error will come up. Clicking continue doesn't change anything, the error will continually come up. When the process is done, there are no files from the ISO on the USB drive.

Here's my code for the command line switch....my application is written in C# and uses the Process class to execute...

                Process unet = new Process();
                unet.StartInfo.FileName = @"C:\tmpdeploy\unetbootin.exe";
                unet.StartInfo.Arguments = "method=diskimage isofile=\"C:\\tmpdeploy\\paragon.iso\" targetdrive=\"" + mySettings.DestinatonDrive + "\"" + " autoinstall=yes";
                unet.StartInfo.WorkingDirectory = @"C:\tmpdeploy";
                unet.StartInfo.UseShellExecute = false;
                unet.StartInfo.Domain = Environment.MachineName;
                unet.StartInfo.UserName = "Administrator";
                unet.StartInfo.Password = secString;

                unet.Start();
                unet.WaitForExit();

in case no one is C# savvy, the command line switch translates to :

unetbootin.exe method=diskimage isofile="C:\tmpdeploy\paragon.iso" targetdrive=<drive letter:> autoinstall=yes"

It works on most systems, but i'm running across many that give this error when extracting. They seem to be all Vista Business systems (32-bit)

Geza Kovacs (gezakovacs) wrote :

Have you tried doing the process manually on one of the machines it fails on (ie launching from command line with the desired command line options), does it fail then? I'd suspect that maybe mySettings.DestinatonDrive is not actually the drive letter (ie "D:\"), but the device ID ("\Device\HardDisk\DR1"), maybe try unit testing that it doesn't contain the string "Device"?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers