Hai all,

Plz help me..

I am using avira boot rescue cd from Usb for computer virus Scanning.

Most of the pc doesn't have Internet for security reason.

Avira doesn't have a way for offline update in rescue cd.

Avira uses ubuntu to boot.

During update, in internet provided pc avira creates a update folder in temp which would not be able to copy.

If we try to copy, permission denied error appears in ubuntu.

It seems avira uses root permission. 

Any way to copy update folder without root permission in ubuntu?

Hi guys. I am in need of your assistance in choosing a sata to usb adapter that will support 2.5'' as well as 3.5'' under heavy usage: booting, copying huge amounts of data. I will need this to be portable, so no external power. Just USB. 

I was thinking of something like this http://cdn.shopify.com/s/files/1/0378/4593/products/USB3Cable_2.jpg?v=1404114351

The problem is that, on all adapters of this type have the power usb connector using only two wires: vcc and gnd which can only take 100mA out of the maximum of 500mA on the standard USB 2.0. Any drive, when under pressure will use more than the 500mA of an USB port, which is why two of these USB ports are required.

Now, based the writings found here https://community.wd.com/t/how-to-eliminate-potential-problems-on-usb-powered-drives-and-keep-them-healthy/7709

 

Each USB port is capable of delivering 500mA @ 5Volts max and each port has built in semiconductor fuse that disconnects when external device power drain exceeds rated power output. This fuse will heal itself once the offending device disconnects. This fuse inherits tolerance of 5-10% of 500mA plus or minus. That means it could be disconnecting either on 450mA or 550mA of current drain.

 

Most of my bought adapters perform like the above: they draw more power, fuse kicks in and the device is longer usable for several minutes.

Any of you guys have a sollution to making an internal drive portable, without any external power supply? I would prefer an external adapter as opposed to an hdd enclosure because the enclosure is hard change the drive.

Thank you

who can make for me script of unreal commander and burnaware in language italian for win7pe se?

I have downloaded script of winrar, it's possible translate in italian?

thanks

This is my first time using xboot, & I've tried running xboot different ways to hopefully stop the problem I have but no luck. I keep getting the error message in the log below:

ERROR REPORT ( 08/22/2016 20:03:29 )
Please submit this error report to developer.
Operating System version  :Microsoft Windows NT 6.2.9200.0
.NET Framework version    :4.0.30319.34014
Error Message            :
Could not load file or assembly 'PGK.Extensions, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f93e897f802ddcb7' or one of its dependencies. The system cannot find the file specified.
StackTrace               :
   at A.V.D()
   at A.V.D(ImageItemBase , ProcessLog )
   at A.FB.D()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Has anyone seen this error message before?

Thank You

Hai,

       I have been booting iso from iscsi disk in local network using below ipxe

Can this be modified to boot from internet anywhere?

Which line should be modified and plz explain the way to make it work...

For the sake of discussion, let's say I have a windows 7 computer that is severely damanged. An 5-year old installation, many programs, and is booting extremely slow, and runs very ver slow. The OS is damaged.

I'm looking for a way to minimally boot windows but not in safe mode. Boot to login screen, login to a user account and that's it. Force it to load only necesesary services, without executing startup entries. I need to do it this way because I have some data to recover that is only available on the user's profile.

Is there any way of accomplishing this?

Thank you

Hey there! :hello:

I have a question regarding how to overcome the three IDE hard disk limit in Virtual PC 2007.

I already created two more 2 GB VHD hard disk images and I want to mount them as drives G: and H: and I want to be able to mount the drives at startup.

However, the draw back is that in any event that I log out, the mounted drives disappear and I need to find a way to forcefully dismount them.

Is there a way to mount the newly created hard disk images at startup and to find a way to prevent the mounted drives from disappearing when I log off? If so, how can it be done?

I've noticed that only Gizmo Drive mounts the hard disk images (VHDs and IMGs) at startup, but it's not 100% reliable.

I just bought a Patriot 128GB class 10 MSD from Fry's Electronics a few days ago. It is exclusively for use in my Note 4, which Samsung states to be compatible with 128GB MSDs. I need to have 3 partitions:

1.90GB exFAT (advantage over FAT32 is larger file sizes over 4GB, which my stock modded TouchWiz ROM recognizes out of the box). I would love to use Ext4 for this partition, but it seems to be only mountable by AOSP/CyanigenMod-based ROMs, whereas TouchWiz ROMs cannot mount Ext4 on MSD without questionable/unreliable hacks. By default Android will only mount the 1st primary partition on an MSD, which is why it needs to have the largest size of the 3.

2. 2nd partition, 25GB formatted as ext4, which is for use with an app called Link2SD.FS must be ext4 because permissions and file ownership must be supported, which exFAT cant handle. L2SD allows to "link"/"bind" apps, odex/deodex files, app data/caches, etc to the 2nd partition, via symbolic links. This is mainly useful for games and other large apps.

3. 1.5GB Linux swap partition, not for use by the ROM/Android itself, but for use with running chrooted/jailed Linux installs (think of it as running a full Linux distro in a VM on Android).

Theoretically, this setup should be fine, but in practice I've found it be slow. Copying files to/from the 1st primary partition can take awhile, when I first set this layout up it took several hours to copy about 12GB of files from the phone's internal storage to Sd. Speeds ranged from less than an Mbyte per sec to 20. Apps linked to the 2nd partition oftentimes run sluggishly, hang for short durations, etc.

Partitions were created with a card reader on a PC via Gparted in Parted Magic. MBR was used. I also checked the alignment of the partitions via parted (CLI version of Gparted). All seemed fine. I dont think the SD is a counterfeit/bum, the Patriot brand is known for reliability, and Fry's isnt known to willfully sell knockoffs/faulty goods. Speed tests with various benchmark tools show the card runs at/near advertised speeds (with a margin above or below rated speeds, of course). I'm thinking this is a matter of improper alignment, not enough space at/before partitiin table start, I'm just not sure. I went with Gparted's default alignments when creating partitions.
 

I'm basically looking for MSD-specific partitioning advice, perhaps recommendations to use other filesystema if need be.

Thanks!

More info, probably not relevant:

Bootloader is unlocked, so I can install custom KitKat/Lollipop ROMs,AOSP ROMs, etc.

Latest TWRP custom recovery installed

Device is rooted with CF-AutoRoot and latest SuperSU

Rom is stock odexed TouchWiz 4.4.4 KitKat firmware released by Samsung, but with minor community mods like busybox preinstalled, zipaligned, etc. All stock Google/carrier/Samsung bloatware is present but can be easily removed

Custom kernel is installed, with support for execution of init.d scripts on boot (otherwise Link2SD wouldnt work), overclocking/underclocking, loop device support, SELinux security status is set to Permissive rather then Enforcing (Latter is KK default value as mandated by Google)

Hello Everybody 

I'm trying to make an AIO windows Installation and Recovery Iso, I'm all successful in the part of merging images and languages, but I'm having trouble integrating the MS DART into the setup process. I have followed the tutorial here , but I'm unable to make it show the options whether to install windows or boot into one of dart versions.
I have edited the bcd into the boot folder and this is the final result:

Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
                        {a8d8adf9-6e05-11e6-82e3-446d57137f02}
                        {3be79aed-6e06-11e6-82e3-446d57137f02}
                        {675e12ac-6e06-11e6-82e3-446d57137f02}
                        {9d548b5c-6e06-11e6-82e3-446d57137f02}
                        {cc681c81-6e06-11e6-82e3-446d57137f02}
                        {e9fc006f-6e06-11e6-82e3-446d57137f02}
toolsdisplayorder       {memdiag}
timeout                 30


Windows Boot Loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows Setup
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No


Windows Boot Loader
-------------------
identifier              {a8d8adf9-6e05-11e6-82e3-446d57137f02}
device                  ramdisk=[boot]\sources\dart10x64.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Diagnostics and Recovery 10 x64
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\dart10x64.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No


Windows Boot Loader
-------------------
identifier              {3be79aed-6e06-11e6-82e3-446d57137f02}
device                  ramdisk=[boot]\sources\dart10x86.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Diagnostics and Recovery 10 x86
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\dart10x86.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No


Windows Boot Loader
-------------------
identifier              {675e12ac-6e06-11e6-82e3-446d57137f02}
device                  ramdisk=[boot]\sources\dart8.1x64.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Diagnostics and Recovery 8.1 x64
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\dart8.1x64.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No


Windows Boot Loader
-------------------
identifier              {9d548b5c-6e06-11e6-82e3-446d57137f02}
device                  ramdisk=[boot]\sources\dart8.1x86.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Diagnostics and Recovery 8.1 x86
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\dart8.1x86.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No


Windows Boot Loader
-------------------
identifier              {cc681c81-6e06-11e6-82e3-446d57137f02}
device                  ramdisk=[boot]\sources\dart7x64.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Diagnostics and Recovery 7 x64
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\dart7x64.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No


Windows Boot Loader
-------------------
identifier              {e9fc006f-6e06-11e6-82e3-446d57137f02}
device                  ramdisk=[boot]\sources\dart7x86.wim,{default}
path                    \windows\system32\boot\winload.exe
description             Diagnostics and Recovery 7 x86
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\dart7x86.wim,{default}
systemroot              \windows
bootmenupolicy          Standard
detecthal               Yes
winpe                   Yes
ems                     No

I guess I'm missing something :\ , If someone can tell me what to change/edit to make it work.

the final result should be similar to this, except it must has a " Windows Setup " to install Windows:

Can someone explain how to inject a filterdriver to WinPE?

I tried it with DISM GUI 4.0, with the WinPE (made with MariumReflect).

I can include the diskmod (0.0.2.2) filter driver, but i have no idea how to activate it.

Regedit works but there a no entries in the registry.

Can somone explain how and what has to be edited?

Thanx in advance,.

BR

Ratte

Hi,

I recently learned that the ZM-VE400 from Zalman is a relabeled iodd device. I also heard from someone on a forum it'd be possible to flash the original iodd firmware onto the relabeled device, but it would require some modification. The ZM-VE400 appears to be identical with the following product: iodd2541.

Does anyone here know how to flash the iodd firmware onto the relabeled device?

One of the motivations is the recent filing for bankruptcy by Zalman. In case they don't continue support, I'd be able to use this alternative route.

Thanks in advance.

I found a promising pointer which I better add here:

• http://sourceforge.net/projects/iodd/

Hai,

       There are five different type of on-board lan ( Intel, broadcom, realtek,etc...) present in our network.

Vhd is present in iscsi target and lan boot works fine for realtek cards.

Is it possible to make it work for other cards just modifiying and adding drivers of specific card?

Without the specific network card present in the pc?

I'm on the first steps of the learning curve for using Qemu within Windows and I started to use the last version of Qemu Manager (7.0).

At the same time, considering the old age of the qemu executables inside Qemu Manager, I'd like to apply some update and so I've downloaded the last binaries from Stefan Weil's page.

The point now is that I don't know how to apply these changes in Qemu Manager (changing its folder structure/content,and how?, what qemu.exe to use?, and so on).

ambralivio

File Name: ProxyCryptGUI
File Submitter: JonD
File Submitted: 30 Nov 2014
File Updated: 16 Aug 2016
File Category: Security

This is an outdated version.
The latest version of ProxyCryptGUI on this site is deprecated... you should look to SourceForge for the latest working version. Here's the link:
https://sourceforge.net/projects/proxycryptgui/

If your are using ProxyCrypt 1.x and you plan to upgrade to ProxyCrypt 2.x, you will want to avoid the use of the Twofish cipher available in version 1.x since it will be unavailable in ProxyCrypt 2. AES or Serpent encrypted containers created with ProxyCrypt 1.x will work with ProxyCrypt 2.x. In all cases, it's always essential to keep backups of your encrypted containers before any updates/upgrades.

Version 2016-02-21:
This is an outdated version... see the link above.
No longer available
 

Version 2015-12-16:
No longer available
 

Version 2015-12-08:
No longer available

Version 2015-11-16:
No longer available

Version 2015-11-01:
No longer available

Version 2015-08-17:
No longer available

Version 2015-08-11:
No longer available

About ProxyCryptGUI:
• ProxyCryptGUI is a free application that provides a graphical interface on a Windows based computer to manage encrypted virtual disk drives using the applications ProxyCrypt and ImDisk.
• The setup file for ProxyCryptGUI includes the required setup of ProxyCrypt and ImDisk.
• All files stored in an encrypted virtual drive can be accessed just as any files on regular disk drives but only after the drive is mounted/opened with the associated passphrase.

Features:
• easily create and mount encrypted disk drives.
• simplified interface for changing the passphrase of encrypted disk drives.
• catalogue listing of encrypted containers.
• automatic location of encrypted containers that are located on removable devices.
• extensive documentation.

Requirements:
• Windows XP, Vista, 7, 8 or 8.1, 32b or 64b
• computer administrator privileges
• CPU with SSE2 instructions

Hello all.

Today, I have a question.

How to change the path boot.ini of NTLDR in Windows XP?.

Normal, Boot.ini located in C:\

Now, I want custom to C:\MyPath\Boot.ini

So, this is possiable?.

Thanks.

By default, the virtual drive shows up as a BD-ROM drive on your computer, so even if you don’t have a Blu-ray drive, you kind of do with the ZM-VE200