mats
Content Type
Profiles
Forums
Events
Posts posted by mats
-
-
With PE1.6 they work with the special driver without problems.
Unfortunally I don't have an blades to test on currently so I can't test PE 2.X.
I would contact HP about this and see if they got a fix.
0 -
The Official answer is NO. Asked MS about it a while ago
Wireless support is not included in PE.
0 -
I like win7 better than Vista but:
-Strip the junk out of it. It still contains way to much stuff that's just a waste of systems. Someone said that you can use Vlite to get ride of it. True in som cases but be aware that using vlite means that MS will not support that box. For us that is a requierment.
Every minute of extra installation time means about 30 000 minutes a year for us. With a IT person costing $100/hour thats about $50 000 for every minute of extra installtion time.
Therefore everything that isn't truly needed (not that MS claims is needed) should be core installed om the Enterprise SKU and the rest should be customizable. MS had this feature for Vista but removed it for some reason (saw it in an waik alpha).
Is there such a huge difference then?
Yes there is. MINWIN will boot from disk and provide network connectivity in less than 40 MB on disk ...
0 -
i dont have those hardware. only flasget is running all the day and when i go home, i see its rebooted nearly once every hour, and i cant dl anything. The problem is about a usbsys file so i dont think its about flashget but i will try other downloader to see. How can i fix this problem? İ installed only a few software. Acdsee, nokia, ultraiso,acronis..a few more. They are not running while this reboot happens. Somone says virtual cd software cause this. So can ultraiso be the reason? But its not running, i did not mount any drive.
Ultraiso or nolia would be my first to guesses. The do install device drivers and The nokia software uses sub to connect to yuour phone right?
0 -
You could use MDT and just load a binary image of your linux polattform
I think there is a read/write driver for ext2 wich should make it possible to use imagex if you could figure out how to format the drive
0 -
Minwin is in its current state a cleanup between kernel and usermode code. In vista and earlier some kernel mode functions made calls to usermode functions wich in turn called other kernel mode functions.
This has been cleaned up to Win7/2008R2 so that kernel mode calls remains in kernel mode.
The bootable testplattform made from minwin was about 35 megs in size and capable of booting from HD and capable of network access the last time i heard anything about it.
Marks blogg should have info on both
. Or listen to his presentations, they are really good0 -
And just to put the final nail in the PAE Coffin.
HW driver must be able to handle PAE systems to work correctly in that enviroment. Since most XP drivers released by third party vendors doesn't PAE on Client Operating Systemes tends to be a bluescreen generating event. For 64 bit systems this problem doesn't exist either
0 -
There is another purpose of the 200 MB partion. Think bitlocker
0 -
Applications wich uses large caches like databases for example. However since the mapping introduces a performace penalty it's better to got to true 64 bit soloutions if possible
0 -
in the list of new good thing in Vista i miss bitlocker, Usb management, ipsec, no more gina, printerpermissions, delta replication of offline files, one offline cache per user, Smartcard based EFS and some more Corp features
If MS would have pushed theese parts instead of gui changes, Vista would have been a hit. As they did it, CIO:s heard gui changes=High costs for education of the users=Not interested instead of hearing Faster and more reliable sync and scure data on laptops=Higher production=more money=Happy CEO
0 -
Hi, i was thinking alot about a "game mode" (not a game version) as it's easy to program already a software that:
- shutdown antivirus, firewall
-
In other words get hacked and have your system used for everything else than gaming.
The right answer is to get the game developers to start writing decent code. Connecting through a firewall is no problem.
Av doesn't use that much of the system that it should be a problem. Optimize the gaming code instead.
0 -
I didn't know you could do it from boot.ini either. It might be a very good way actually since some computers won't boot on the more generic haltypes.
We sav this problem and used acpi_pc hal wich boots anything we got so far
but being able to set the hal up front may be even betterWe did the exact same thing as you described - the acpi_pc HAL would boot everything...while until we got the latest Lenovo T400's in. The processor in that model doesn't support the ACPI_PC HAL - apparently Intel decided to remove some instruction sets that were outdated in favor of newer ones (don't quote me on that). I've now decided to 'fork' the image since alot of the older computers are too old now and not being used as much. The dual core's really do pack a good punch compared to the P4's.
Sometimes the world can be pretty funny. Guess what. I got a T400 on my hand's now
. Did a quick patch for it.
hal=objWSHShell.RegRead("HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\HardwareID")
If hal(0)="acpiapic_mp" Then
set objfile=fso.getfile("C:\boot.ini")
objfile.attributes=0
line= objini.Readstring("operating systems","multi(0)disk(0)rdisk(0)partition(1)\WINNT","C:\boot.ini") & " \kernel=ntkrnlmp.exe \hal=halmacpi.dll"
objini.writestring "operating systems","multi(0)disk(0)rdisk(0)partition(1)\WINNT",line,"C:\boot.ini"
objfile.attributes=39
end if
The Objini object is just a simple ini read/write class in an activeX dll we write to stop bloat every script with it.
0 -
Winpe 1.X is also available to customers with SA agrements
0 -
Yes there is. Compile it 64 bit
If it's 64 bit code it will be run native. If it's 32 bit it will be handled by WoW64 since it isn't 64 bit wich is that the OS requires so the "simple" way to target the right enviroment is to compile it for that enviroment
0 -
WinPE 64 does not contain the 32Bit windows subsystem. In other words it will only run 64 bit native apps.
Vista/2008 and XP/2003 64 bit editions has a subsytem for runing 32 bit apps. Therefore some apps may run under a full os but fail under PE
0 -
Thanks for the info.
Now i know that the current soloution won't last much longer. Time to start thinking about something new then, win 7 maybee?
0 -
There is versions of DD for win32
0 -
There is WMI support in both pe 1.6 and 2.X. It's not a full support but the must useful classes are implemented.
MDT for example uses WMI to detect chassietypes
0 -
I didn't know you could do it from boot.ini either. It might be a very good way actually since some computers won't boot on the more generic haltypes.
We sav this problem and used acpi_pc hal wich boots anything we got so far
but being able to set the hal up front may be even better0 -
I have to throw my 2 cents in here. I used to be a big fan of imaging, back in Windows 3.1 days. When Win95/NT came out I battled with imaged deployments for a year. I finally started doing it the "right" way by using scripted deployments.
Look, it's plain and simple, and it's been a fact of Windows deployments for over 10 years - Imaged deployments suck! If you want to properly deploy Windows NT/2000/2003/XP you use unattended scripted installations. Yes, they're hard to do, Yes - they take forever to install. But it's the only way to the best Windows installation possible. However, once you got it setup it's easy to maintain. Imaged deployments are inherently unstable - especially if you image the applications along with the OS installation.
I always argue with inexperienced admins about imaged deployments, because they are just being lazy. They always mention "well so and so does it", or "HP and Dell use images to deploy their systems". Well, ya they do - and they are idiots. They hired noobs to do their deployments. Recently HP got bit in the a** because they stupidly use imaged deployments to roll out XP.
Imaged deployments actually get me angry, from having to deal with their issues over and over again throughout the years. They make Windows unstable and I firmly believe that the reputation of Microsoft Windows being unstable is directly related to crappy imaged deployments.
So get off your a** and learn to do scripted installations!
Well my reply to this is to learn how to do a proper image
The trick is to have proper methods and routines to create your image. If you just do it by hand and feel, then you will have a mess. If you do in a structured way you will have a well working soloution that saves a lot of time and money, troubleshoting is easier too since you will have an identical machine to do it from.
The best way to accive this is actually to use a scripted installation to generate the image based installation.
In our production enviroment we uses an in house developed four step method:
0. Operating system and mui
1. Hotfixes/patches and apps
2. Gui Adjustments
3. Defrag and sysprep
for each of these steps we take a new image, therefore it's wery rare that we do a new 0 image. Uasally we just load that up from disk, and goes into step one, adds the last months uppdates, patches and changed apps. Step two is mostly automated but some GUI tweaks requiers manual adjustments, therefore we have a checklist for that, Step three is fully auto with the exption of adjusting sysprep inf for new massstorage controllers. This gives us very stable "fat" images containing everything an ordinary user requires to start working.
Doing this the scripted way takes about 6-7 Hours, With imaging it taks 30 min to reinstall a PC. This means that we don't do deeper troubleshoting of software problems anymore. Helpdesk uses 15 max to try and fix it, if they can't they reinstall the PC remotly or asks the user to press F12 to start the reinstallation manually. A coffeebreak (about 30 min) later he/she has a working machine again. If you compare that with dispatching a tech and in worst case having the box replaced, imaging saves time for the users and lowers our operating costs. Especially if you have many offices and don't have local techs on all locations
Sure it takes some time to maintain the images but with 19K boxes it's sufficient to save a few minutes/a box to pay for the image handeling time. The rest is a bonus.
0 -
I prefer to let sysprep do the switch by setting updatehal or updateuphal values depeninding on wether it's a multi or singleprocessorbox.
If you are using MDT or SCCM this can be integrated into the task sequence rather easy
0 -
64Bit doesn't support 32 bit files like a vb6 application. Therefore you are getting errors.
I don't know of any other solution to this but to migrate to something else. VBscript maybe or autoit.
If you need to do something hreavy I have had to got to C++
0 -
This is another way
0 -
Another way is to take a look att MDT. it's Ltiapply.wsf has a /Pe switch to install PE to the harddrive. It needs a small change to make pe the second boot option though
0
RDP Server under WinPE
in Windows PE
Posted · Edited by mats
Long time since I posted here but now I have run into an interesting question.
Is there an way to get an RDP server running under winpe (not a client connecting to some other server).
The idea is to find a Open way to do the same thing as DART remote admin does for WinPE if you have SA.
I have seen sharing applications like http://blogs.msdn.com/b/rds/archive/2007/03/23/writing-a-desktop-sharing-application.aspx but they seem to be missing something since they do display a big Pause sign instead of the picture.
Edit: To get that far you must include rdpcore.dll and rdpencom.dll with your code and rdpencom must be registered.
The FreeRDP project is supposed to have a server to but I haven't been able to figure out how to build it.
I know there are X number of VNC based soloutions out there but I want something based on RDP.