Jump to content











Photo
- - - - -

Rufus v1.3.0 has been released


  • Please log in to reply
208 replies to this topic

#201 steve6375

steve6375

    Platinum Member

  • Developer
  • 6566 posts
  • Location:UK
  • Interests:computers, programming (masm,vb6,C,vbs), photography,TV,films,guitars
  •  
    United Kingdom

Posted 19 February 2015 - 06:03 PM

https://github.com/p...andline_support

 

You could try RMPartUSB (accompanies RMPrepUSB) followed by an XCOPY command?


  • otto.johannes.wismar likes this

#202 otto.johannes.wismar

otto.johannes.wismar
  • Members
  • 2 posts

Posted 19 February 2015 - 06:53 PM

I will Check it out

#203 freesoft00

freesoft00

    Member

  • Members
  • 30 posts
  •  
    China

Posted 25 February 2015 - 11:24 AM

Non English user feedback in a bug

 

The following is the online translation, do not know whether you can understand.
Open the Rufus, format the disk U for Syslinux 4.07 or Syslinux 6.03, in the case of turning off Rufus, re format the disk U for other boot mode, there will be unable to access the U disk device error.
If you close a Rufus open again, and then format can be.

 

Format MBR, PBR to BOOTMGR or NTLDR does not support the Rufus, whether you can add up
Whether can support the U disk partition to many, a fat, a NTFS, u disk boot that can create supports both BIOS and UEFI support
Grub only 0.4.6a, whether you can add 0.4.5c

 

rufus.log file

 

Rufus version: 2.0.632 (Beta)
Windows version: Windows XP SP3 32 bit
Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06
Grub versions: 0.4.6a, 2.02~beta2
Locale ID: 0x0804
Found USB 1.0 device 'aigo Miniking USB Device' (093A:2510)
Using autorun.inf label for drive G: 'HLSTUDIO'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 123, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x005A2332
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: NTFS (0x07)
  Size: 967.0 MB (1013971968 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE1 for write access
Will use 'G:' as volume mountpoint
I/O boundary checks disabled
Analyzing existing boot records...
Drive has a Syslinux Master Boot Record
Volume has an unknown Partition Boot Record
Deleting partitions...
Clearing MBR/PBR/GPT structures...
Erasing 128 sectors
Partitioning (MBR)...
Closing existing volume...
Waiting for logical drive to reappear...
Formatting (NTFS)...
Using cluster size: 4096 bytes
Quick format was selected
Creating file system: Task 1/12 completed
Creating file system: Task 2/12 completed
Creating file system: Task 3/12 completed
Creating file system: Task 4/12 completed
Creating file system: Task 5/12 completed
Creating file system: Task 6/12 completed
Creating file system: Task 7/12 completed
Creating file system: Task 8/12 completed
Creating file system: Task 9/12 completed
Creating file system: Task 10/12 completed
Creating file system: Task 11/12 completed
Creating file system: Task 12/12 completed
Format completed.
Writing master boot record...
Drive has a Zeroed Master Boot Record
Set bootable USB partition as 0x80
Using Syslinux MBR
Found volume GUID \\?\Volume{b5d2deac-089b-11e4-8160-005056c00008}\
Installing Syslinux 4.07...
Successfully wrote 'ldlinux.sys'
Opened drive \\?\Volume{b5d2deac-089b-11e4-8160-005056c00008} for write access
Successfully wrote Syslinux boot record
Successfully remounted Volume{b5d2deac-089b-11e4-8160-005056c00008}\ on G:\
Finalizing, please wait...
Created: G:\autorun.inf
Created: G:\autorun.ico
Successfully remounted Volume{b5d2deac-089b-11e4-8160-005056c00008}\ on G:\

Found USB 1.0 device 'aigo Miniking USB Device' (093A:2510)
Using autorun.inf label for drive G: 'HLSTUDIO'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 123, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x005C102D
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: NTFS (0x07)
  Size: 967.0 MB (1013971968 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes

Format operation started
Requesting disk access...
Opened drive \\.\PHYSICALDRIVE1 for write access
Will use 'G:' as volume mountpoint
I/O boundary checks disabled
Could not get exclusive access to device \\?\Volume{b5d2deac-089b-11e4-8160-005056c00008}: [0x00000005] 拒绝访问。
Could not lock volume
Re-mounted volume as 'G:' after error

Found USB 1.0 device 'aigo Miniking USB Device' (093A:2510)
Using autorun.inf label for drive G: 'HLSTUDIO'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 123, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x005C102D
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: NTFS (0x07)
  Size: 967.0 MB (1013971968 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes
Found USB 1.0 device 'aigo Miniking USB Device' (093A:2510)
Using autorun.inf label for drive G: 'HLSTUDIO'
1 device found
Disk type: Removable, Sector Size: 512 bytes
Cylinders: 123, TracksPerCylinder: 255, SectorsPerTrack: 63
Partition type: MBR, NB Partitions: 1
Disk ID: 0x005C102D
Drive has a Syslinux Master Boot Record
Partition 1:
  Type: NTFS (0x07)
  Size: 967.0 MB (1013971968 bytes)
  Start Sector: 2048, Boot: Yes, Recognized: Yes

 



#204 Akeo

Akeo

    Frequent Member

  • Developer
  • 295 posts
  •  
    Ireland

Posted 25 February 2015 - 12:38 PM

The following is the online translation, do not know whether you can understand.

That's fine. no worries. ^_^
 

Open the Rufus, format the disk U for Syslinux 4.07 or Syslinux 6.03, in the case of turning off Rufus, re format the disk U for other boot mode, there will be unable to access the U disk device error.
If you close a Rufus open again, and then format can be.

 
Thanks for the report. I've reproduced the issue with Syslinux/NTFS. And just to clarify the steps:

  • Format the drive as NTFS, using bare Syslinux 4.07 or 6.03
  • Without quitting Rufus, format the drive to FAT32 using FreeDOS → Fails on "Requesting Disk Access"
  • Re-launch Rufus an try FreeDOS again → Works.

The same does not seem to happen when formatting for Grub/NTFS or even Syslinux/FAT32 as the first step, so it looks like we may be keeping some handle open when formatting for Syslinux/NTFS. I'll see if I can figure out why disk access is being prevented.
 
Note that this is not an issue with Rufus 1.4.12, as this version doesn't allow Syslinux on anything but FAT (and for the purist(s? :D) out there, Rufus probably shouldn't allow Syslinux 4.07 on NTFS, since 4.07 doesn't actually support NTFS but since this is only enabled from advanced, I don't really care if that's what a user wants to try)
 

Format MBR, PBR to BOOTMGR or NTLDR does not support the Rufus, whether you can add up


I'm not planning to add bare bootmgr or ntldr support, if this is what you're asking. First of all, this would greatly increase Rufus' size, and more importantly, these components are proprietary and owned by Microsoft, so I don't have legal rights to redistribute them in Rufus. AFAIK, the only way a user can legally access bootmgr or ntldr is when they come as part of an official Windows image distributed by Microsoft.
 

Whether can support the U disk partition to many, a fat, a NTFS


If this request is about giving users the ability to create multiple partitions from Rufus then no, that's not something I'm planning to add.
 

u disk boot that can create supports both BIOS and UEFI support


Most Linux images should support dual UEFI/BIOS by default (provided the ISO supports it). I know for instance that the USB created by Rufus from a tails ISO can be booted in either BIOS or UEFI mode.
 
As to Windows images, dual UEFI/BIOS is disabled by default. Please see here for the reason. But this can be re-enabled through the Alt-E cheat mode.
 

Grub only 0.4.6a, whether you can add 0.4.5c


I upgraded Grub4DOS from 0.4.5c to 0.4.6a between BETA 1 and BETA 2, as I believe it is stable enough and there was an official release by chenall. I am not planning to revert back to 0.4.5c or provide multiple versions of Grub4DOS.

I keep saying this on regular basis, but please remember that Rufus is NOT aimed at sysadmins or even power users. So I have no plans to add every option under the sun to help with sysadmin tasks.

If you need a larger set of options for your boot process, I'd recommend RMPrepUSB and/or Easy2Boot.



#205 freesoft00

freesoft00

    Member

  • Members
  • 30 posts
  •  
    China

Posted 25 February 2015 - 02:09 PM

I mean I'm not integrated with BOOTMGR or NTLDR, but want to make Rufus support nt6 NT5 boot or boot code
Be similar to  bootsect /nt60 c: /mbr

 

 

 

Syslinux does not support NTFS, so when choosing NTFS format screen out Syslinux better.


Edited by freesoft00, 25 February 2015 - 02:23 PM.


#206 Akeo

Akeo

    Frequent Member

  • Developer
  • 295 posts
  •  
    Ireland

Posted 25 February 2015 - 02:16 PM

I see what you mean.

 

Still not planning to add it, as very few people apart from power users should ever need that feature and, unlike Grub or Syslinux, Windows does come with the bootsect utility, so users already have everything they need if they want to install that boot code. I much prefer spending time on features that are not already provided by Windows.



#207 Akeo

Akeo

    Frequent Member

  • Developer
  • 295 posts
  •  
    Ireland

Posted 27 February 2015 - 10:40 AM

  • Format the drive as NTFS, using bare Syslinux 4.07 or 6.03
  • Without quitting Rufus, format the drive to FAT32 using FreeDOS → Fails on "Requesting Disk Access"
  • Re-launch Rufus an try FreeDOS again → Works.

 

This should now be fixed with the latest BETA. Please let me know if you still see an issue.



#208 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13493 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 27 February 2015 - 11:19 AM

Windows[1] does come with the bootsect utility, so users already have everything they need if they want to install that boot code.

 

[1]Starting with Windows Vista :ph34r:

 

:whistling:

 

Users of previous versions of the Windows operating system will need to get a third party utility, or get a WAIK/ADK or get just the bootsect.exe through the use of the GetWaik tool (or similar), just for the record:

http://www.msfn.org/...-the-huge-isos/

and - only in case of *need* - some self-promotion :w00t::

http://www.msfn.org/...sions-compared/

 

On the other hand WHY EXACTLY one would want to use anything before Vista :ph34r:, like - say - XP or 2K? :unsure:

 

The developer of Rufus - while still maintaining for the moment support for XP - seriously frowns upon the use of his tool on those "retired" systems (actually on the use of such "retired" systems)::

 

 

 


Now, that's not to say I'm planning to drop XP support from Rufus anytime soon, especially as I spent way too much time adding support for it - and even for the upcoming 2.0 release I had to do a lot of XP specific work, but that doesn't mean I have to like it or will refrain from chastising anyone who's still trying to justify the use of a retired OS...

 

And if you don't use any  NT 5.x version of Windows you surely don't need to have it's bootsector anyway....

 

:duff:

Wonko



#209 freesoft00

freesoft00

    Member

  • Members
  • 30 posts
  •  
    China

Posted 03 March 2015 - 10:32 AM

 

This should now be fixed with the latest BETA. Please let me know if you still see an issue.

 

 

My feedback problems have been solved in the new test version, thank you!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users