Success - Integrating dummy.sys into LiveXP - BootSDI
#26
Posted 19 August 2009 - 01:39 AM
very nice
uploaded to LiveXP server
we are waiting other Success stories from you
#27
Posted 17 September 2009 - 09:37 AM
#28
Posted 19 September 2009 - 07:03 AM
Latest version uploaded in first post.
#29
Posted 25 September 2009 - 01:07 PM
i tried all those steps..but i couldn't make my usb..
can some one plz guide me how to make it.step to step plz.
thank u//
#30
Posted 25 September 2009 - 01:29 PM
Please also try to use the search option.
#31
Posted 25 September 2009 - 01:35 PM
http://www.boot-land...?showtopic=4900
http://www.boot-land...?showtopic=7512
Further links from there might also be useful.
Look for links to tutorials in the signatures of online and wimb.
#32
Posted 25 September 2009 - 07:02 PM
Can you be clear about what you are trying to achieve? This may not even be the right thread for what you are trying to do.
Please also try to use the search option.
hi..i want to make a live windows usb.not a boot usb to install windows.
i hope the two links that our friend gave me work.
thank u
#33
Posted 25 September 2009 - 09:40 PM
It might be helpful to add the info description from the script to you're first post so people can know at quick glance what this script does. Very useful. Haven't tested yet.
At reading you're first post, it seemed as if you where saying that you could boot LiveXP from you're USB stick and this script made it be mounted as a Hardrive.
You have to plug in the USB stick during boot time. Script Depends on USB Mass Storage Devices script, which MUST be selected for this to work.
In case the USB key is plugged in AFTER booting LiveXP, MountStorPE can be used to mount the partitions. MountStorPE is available on LiveXP project under Apps\System.
#34
Posted 25 September 2009 - 10:09 PM
USB Mass Storage Dummy Filter Driver Script
USB Mass Storage Devices Script
But I still only see the USB stick as removable drive
Test in adding USB stick after boot and before booting and both times they are seen as removable devices
USB inserted after bootup
USB inserted after before bootup
#35
Posted 25 September 2009 - 10:23 PM
test with enableing RemovableDevicesCombo.script & vUSBDummyDisk.Script from LiveXP server. If exists Disable USBSupport.Script.
#36
Posted 26 September 2009 - 01:47 AM
Hi The Hive,
test with enableing RemovableDevicesCombo.script & vUSBDummyDisk.Script from LiveXP server. If exists Disable USBSupport.Script.
Used NativeEx and added v3 RemovableDevicesCombo.script from LiveXP and & vUSBDummyDisk. After booting and testing it. The USB drive seemed to load after inserting it after booting but it would not work. I had to reboot to see the USB as a drive and mounted properly. So I was thinking that maybe the NativeEx Script was older and it seems that it is. Its version 5 vUSBDummyDisk. So Im testing using new version 07. Same thing happens when using updated script.
USB in after bootup Sees USB But not working
USB in after rebootup Sees USB and working
So only after a reboot does it see it as a Hard Drive and the USB is mounted properly.
#37
Posted 26 September 2009 - 01:57 AM
are you saying, mounstorpe not working properly ! (or maybe i misunderstand !)In case the USB key is plugged in AFTER booting LiveXP, MountStorPE can be used to mount the partitions. MountStorPE is available on LiveXP project under Apps\System.
#38
Posted 26 September 2009 - 06:18 AM
#39
Posted 26 September 2009 - 05:04 PM
No, I did not have mounstorpe script included in test. The following test does.on the interface of vUSBDummyDisk.Script there is bolded text
are you saying, mounstorpe not working properly ! (or maybe i misunderstand !)
Testing using RemovableDevicesCombo.script, vUSBDummyDisk.script, & mounstorpe.script.
Had mounstorpe autostart.
Inserted USB stick and MountStorPE says it mounted it as C drive.
But when you try to open the C drive Windows reports Missing MSVFW32.dll file
Same when doing a reboot and having the USB Stick already inserted.
AVICAP32.dll missing once you have MSVFW32.dll in System32 folder
After adding those two files to system32 folder nothing happens. C drive wont open.
#40
Posted 26 September 2009 - 05:59 PM
Hi The Hive,No, I did not have mounstorpe script included in test. The following test does.
Testing using RemovableDevicesCombo.script, vUSBDummyDisk.script, & mounstorpe.script.
...
Inserted USB stick and MountStorPE says it mounted it as C drive.
...
But when you try to open the C drive Windows reports Missing MSVFW32.dll file
Same when doing a reboot and having the USB Stick already inserted.
msvfw32.dll-> Microsoft Video für Windows
i guess there is some autostart-content on your usb stick.
and autostart.exe wants to play a clip?
what are the files in root of your usb stick?
Peter
#41
Posted 26 September 2009 - 06:32 PM
AutoRun.exe
AutoRun.inf
Start.exe
Documents and Settings
Program Files
Recycled
temp
WINDOWS
Based on what you said fxscrpt. I did a right click on C drive and selected the Open option and the contents from the USB Stick C drive showed up. So it is when you have as you said a AutoRun something in the USb Stick that you will get the 2 missing files things mentioned earlier. Depending or the requirements of the Autorun.
Another problem
If you use the icon to safely unplug the USb Stick from its C drive location and then reatach it to the USB again. It seems the USb Stick is working and recognized by the Usb Safely Remove Hardware Icon but MountStore will not mount it to a Drive again. Nothing shows up on the Windows Explorer. Also tried it with another USB Stick. Same result. The second one also had a Autorun but it was not mounted as a drive.
#42
Posted 26 September 2009 - 09:44 PM
Hi TheHive,Another problem
If you use the icon to safely unplug the USb Stick from its C drive location and then reatach it to the USB again. It seems the USb Stick is working and recognized by the Usb Safely Remove Hardware Icon but MountStore will not mount it to a Drive again. Nothing shows up on the Windows Explorer. Also tried it with another USB Stick. Same result. The second one also had a Autorun but it was not mounted as a drive.
this issue is caused by disk.sys and exists only for xp builds. see here
by unloading drivers for your last disk , disk.sys is marked for deletetion , but cannot be unloaded from memory.
(and will never start again in this session)
this will never happen, if you have minimum one another disk in your system (e.g second usb stick or fixed disk),
because the pnp manager will not make the attempt to unload disk.sys.
(no problem for real pc's, they should have at least one fixed disk)
if you unmount your last disk, the only workaround is to
copy disk.sys to another location and alter corresponding ImagePath of disk service.
Peter
#43
Posted 27 September 2009 - 02:05 AM
So if you have a USB Mouse or Keyboard and then Insert or de insert a USB stick it should recognized in a real PC. That is since those are USB Peripherals.
#44
Posted 30 September 2009 - 12:52 AM
#45
Posted 30 September 2009 - 11:21 PM
Something is causing the Loading into memory but not actually showing the Vmware program gui nor the boot up of the ISO.
I have to Terminate vmware-Vmx.exe. and then rerun Vmware script and the Vmware gui with the ISO Boot Process comes up. If you click on the Stop button in Winbuilder, the vmware-Vmx.exe stays in memory. The Original NativeEx one doesnt do that.
I like the way the NativeEx Vmware works. It just needs the extra options added.
Can you attach the new Vmware.Script. With changes.
Redownloaded the LiveXP Script for Vmware and same result as reported.
When Vmware Script is suppose to launch ISO in Vmware the vmware-Vmx.exe is just left in memory.
When The stop button in the Vmware Script is pushed the vmware-Vmx.exe is still left in memory.
As you predicted. As long as there is a HD. The USB problem of not being able to reinsert the USB stick and not be recognized is not happening. You can remove and re-add the USB stick and it will be mounted as a Drive.BTW: is USB unmount/mount problem fixed?
#46
Posted 30 September 2009 - 11:46 PM
Does this need to be a hard drive or is it fine if you have a floppy drive also, I mean to keep the disk.sys active?
#47
Posted 01 October 2009 - 02:14 PM
@fxscrpt/@TheHive,
Does this need to be a hard drive or is it fine if you have a floppy drive also, I mean to keep the disk.sys active?
Wouldn't floppy.sys be active then?
http://alter.org.ua/soft/win/floppy/
My guess is that it could be any "virtual device", using VDK or VSS or IMDISK, but not a "floppy", i.e. not VFD.
jaclaz
#48
Posted 01 October 2009 - 02:44 PM
Thanks TheHive,...
I like the way the NativeEx Vmware works. It just needs the extra options added.
Can you attach the new Vmware.Script. With changes.
i will add the option to nativeEx version and post here.
if there is no issue , we have to find the reason for issue of livexp version.
Hi oriensol,@fxscrpt/@TheHive,
Does this need to be a hard drive or is it fine if you have a floppy drive also, I mean to keep the disk.sys active?
i tried almost everything , it has to be a hard drive.
However, if your real pc is not diskless, there will be no issue.
Peter
Edit:
TheHive , please try attached script.
It's pure nativeex version + virtual hdd option.
(i cannot test, because this script does not detect newest vmware player on x64, but i guess it will work)
Hi Peter, we try to bring to light.But which option / feature makes the troubles?
Peter
Attached Files
#49
Posted 01 October 2009 - 03:01 PM
I did not follow this dummy.sys topic because it is out of my scope.
Today I saw that VMWare.script is affected.
What is the issue?
There are some differences between the NativeEx script and the LiveXP version.
But which option / feature makes the troubles?
Peter
#50
Posted 01 October 2009 - 03:03 PM
Lancelot was talking of a floppy and I thought it was for this. So, I asked.
Lancelot's idea was to have a 'very small sized' drive loaded via grub4dos/firadisk for this situation using a script.
Was thinking of a small script under, say, Optimizations for this. I have this ready almost.
What would be the smallest sized hard disk that we can create? 1 MB, I guess, based on mkimg.cmd. We could even gzip it.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users