Lvrt.dll Error

I am using the LabView RTE 8.2.0.4002 to execute a LV app that was built in LV 8.2. My app sporadically crashes. The output error file says the error is in TDUtility.cpp (1432) and sometimes (1041), Unexpected: 8, 4, tc: 48, 48. The PC Event log just reports that my application died and that the faulting module was lvrt.dll version 8.2.0.4002. The Microsoft error log shows that I received an Exception Code: 0xC0000005. My file reports the OS is Windows NT, OS Version 5.1, but the PC is running Windows XP, Service Pack 2.
Any ideas?
Solved!
Go to Solution.

Hi bfieldi,
I am not sure what the Unexpected: 8, 4, tc: 48, 48 message is referring to, but I wouldn't think it would be a typecast. Try the ideas that Karunya posted if you can, and if you want to send your error log in to National Instruments, you can choose to report the error when you get your TDUtility.cpp message. This will supply more information about what is happening.
Regards,
Stephen S.
National Instruments
Applications Engineering

Similar Messages

LVRT.dll error everytime I build a deployment

HI all,
I have struggled with this for 2 days now and tried to use the forum to figure this one out, but I cannot. I have built quite a few deployments before, however, when I try to put a new deployment on a clean Win7 32-bit PC, I get the same issue:
Whenever I try to run the deployment I get the lvrt.dll error...please see JPEG. I am not sure why I am getting this. However, I have two concerns that may be causing it.
1. If you look at the error, it is looking in the Program Files (x86) folder....I don't have that folder on my Win 7 32 bit machine....only Program Files.
2. It seems like when I run the deployment, it is totally skipping the model. I believe this because the error it gives is for a sequence in main, and I have a vi call in the model. However, i do have the cfg folder in my workspace.
Any ideas?
Thanks,
Ryan
Attachments:
error.jpg ‏105 KB

Hi, I am using 4.2. I believe I have solved that issue. It was an issue with the wrong engine below loaded.
However, I am stuck here now. When I build, I get the following warnings, and I cant seem to solve it. Please advise. I realize it wants me to add some paths in the search directories but I'm not sure exactly what it should be.
Thanks,
Ryan
Warning: There is no relative path between the following files. You may need to add a path to your search directories.
From [TestStand]\Components\Models\TestStandModels\FT_ParallelModel.seq to [Installation Directory]\vi\user_stats.vi
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\SeqEdit\layout_Small Screen Example.bin
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\SeqEdit\layout_Large Screen Example.bin
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Users.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\ToolMenu.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TeststandPersistedOptions.opt
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TestStandModelReportOptions.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TestStandModelModelOptions.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\TestExec.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Templates.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\StationGlobals.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\PLPropertyLoader.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Filter.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\EngineParts.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\DeploymentUtilityOptions.ini
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\DeploymentUtility.log
From [Installation Directory]\TS\MF_Final_Test.tpj to [TestStand Application Data Directory]\Cfg\Deployment Utility RecentFiles.ini
+++++++++++++++++++++++++++++++++++++++

Lvrt.dll error in application

Hi, I have built an application from my development PC and I am running it on a target PC. The application crashes regulary on the target PC, within 20 min. Windows displays an error measage that states that lvrt.dll caused the failure. I have been searhing the forum for answers, and found other people with the same problem, however there were no clear solutions to the problem. Does anyone have a solution?
My labview version is 8.5.
My hardware is a CompactDAQ chasis, with modules 9472, 9265, 9205. Moreover I am reading out temperatures from an Agilent 34970A though a GPIB interface.
With kind regards,
Jesper

I too have been experiencing this problem, only with 8.2. I have
a built application that crashes semi-randomly on my development
machine - XP blames LVRT.DLL. I bundled the 8.2 LVRT.DLL into my
build as suggested, that didn't help. The application thus far is
just a fairly complicated GUI with no hardware being addressed (yet)
and no external libraries being called (yet).
Insight, anyone?
Thanx.

Lvrt.dll error on Windows XP

I had an application built using LabView 5 on Win98 system and it was running perfectly, I decided to upgrade the system to Windows XP,then, i used Labview Run-Time Engine 5.1.1, i was surprized when the application ran perfectly also (I know that 5.1.1 works only till Win2000!!!), BUT, after 10 to 15 minutes from idle process, i get an error from WinXP saying that there was a problem in my exe file because of (lvrt.dll), when i restart the application it runs OK.
I'd like to add more info:
- The application is using Traditional DAQ Card.
- The application includes ActiveX & Networking.
- I don't have the source code to modify anything.
Any one has a clue what to do to avoid this error????

Thanks Jeremy, But i have to use a powerfull machine with high configuration, the processor of the machine is 800 MHz Bus Speed, which the 98 can't run on, so i have to use either 2000 or XP, i forgot to tell you that on 2000 i get an error when i try to start the application and when i click ok, it runs perfectly !!!! kind of complicated isn't it????
I can't come up with a solution, can any one????!!!!

System error message and application crash - ModName: lvrt.dll Offset: 00080a6a

I'm running into an error message which is proving particularly difficult to debug. After my built application has been running for some time, a windows system error will pop up telling me my application has done something bad and needs to be shut down (and sorry for the inconvenience). Clicking through to the "see what the error report contains" page reveals the issue as being in the lvrt.dll module at offset 0080a6a.
This unfortunately doesn't mean much to me.
On some occasions when I click "Don't Send", another error message pops up informing me there is "Not enough memory available to complete this operation".
The program will typically run between 8 and 24 hours before the error occurs, though I've had it run error-free for upwards of 48.
My program is unfortunately fairly large, and depends on communication with proprietary hardware so can't be uploaded in a functional state. In general terms, the body of the program (which is executing when the error occurs) involves RS-485 serial communication and simultaneous display of data to 7 continuously updating strip charts (producer-consumer design), along with envalope detection and RMS calculations in real time, all of which is multiplied by two parallel channels (around 1Mb/s data rate for each). The data is also buffered and stored in binary files for later review. Binary files are closed and a new one is opened for every 10 minutes of data collection (approx 50MB of data).
There are also about 40 user controls associated with each channel, and are polled periodically (a couple times a second). The crashes occur during over night tests, however, when there is no user input. Globals are used for inter-panel communication, but no global is written to in more than one location (most are read in multiple locations).
I know this is a bit of a shot in the dark here, but does the lvrt.dll error at offset 00080a6a mean anything to anyone? Are there any "typical" causes for a failure in lvrt.dll having to do with prolonged high data rate serial communications? For reference, this has occured on multiple machines, but all the machines it has occured on are identical out-of-the-box laptop models running XP 32. I'm going to try to run an overnight test tonight on the development machine and see if I get any different results (Vista 64 vs Windows XP 32).
I can't say my hopes are high with this one, and I'm gonna continue to comb over the code for any possible conflicts, but any insight would be appreciated.

Claire,
Next time the error message comes up I will take a screenshot of it for you. Unfortunately that may not be until Monday, as tonight is the soonest I'll be able to run another long-term test. The time between failures is the most frustrating part to debug!
There are no errors on compiling or building the application in LabVIEW. My testing has been done mostly on the distribution laptops in application form, with no LabVIEW dev tools installed, Windows XP 32 bit.
The overnight test I attempted on the development machine (within the LabVIEW environment) welcomed me the next morning with a rebooted machine, and so I wasn't able to see an error message (if there was one). Vista 64 on the development machine. Reviewing the data files, I got about 9 hours worth before the crash.
Given the time between failures and the large volume of data I'm passing around, this seems like memory leak type behavior. I'm a bit confused by the fact that it seems to fail in lvrt.dll every time, though. I'm don't know what that indicates, if anything.

System error 988 whlie loading the LabView eun-time engine (C:\Program file\....\\lvrt.dll)

I am trying to use NI devices with Lazarus (there is no pascal section, so I post here).
When I try to run my application:
DAQmxBaseCreateTask('TaskHandle', TaskHandle);
DAQmxBaseCreateAIVoltageChan(taskHandle,'Dev1/ai0','',DAQmx_Val_Cfg_Default,-10.0,10.0,DAQmx_Val_Volts,'');
I get the following error message:
„System error 988 while loading the LabView eun-time engine (C:\Program file\....\\lvrt.dll)
nidaqmxbaselv requires a version 2010 (or compatible) LabView run-time engine. Please contact the vendor of nidaqmxbaselv to correct this problem.“
I installed LabView run-time engine 2012, but I still get the same error.
Then I tried to install LabView run-time engine 2010- the same result.
I removed LabView run-time engine 2012- same result.
I tried to install LabView run-time engine 2010 again (since I did not see it in the add/remove list)- then I noticed, that the installer shows „A newer version is already installed".
What shall I do?

Hi,
   Can I ask the same question too?
   I am using
   Windows 7 sp1 x64
   Visual Studio 2010 pro
   NI USB-6009
   ni-daqmx base 3.4.5
I created a empty win-32 console project and putted the ANSI C Example program: acquireNScans.c with the include file and lib file of nidaqmxbase in the same folder. I added this line on the top of the source code #pragma comment(lib,"nidaqmxbase.lib"), built without any error. When I tried to run it, I got this same message.
  I tried changing to shared dll mfc and delaying linking lvrt.dll, but did not work.
  Looking forward to your reply.
all the best.

PXI RT 8.6 crash with error lvrt.dll load address 0x1924000

I have an application developed with LabView RT 8.6 that run 24h/day and randomly crash evry 3-10 day with this error:
LVRT.DLL load address 0x1924000. Attached I put log file available after restarting PXI.
I dont found any information on this error, and it's very hard to found the soluction... any idea?
Attachments:
lvrt_err_log.txt ‏66 KB

Application was developed with LV 8.6, actually I have installed a LV 8.6.1 in my lap top where I develope the application. I attach some print screen of configuration of PXI.
Application running on PXI consist of several never-ending loop, one of this is a time-critical loop where I from CAN, DAQ, and I send data via CAN. There is other Hardware-timed loop that comunicate via TCP/IP with PLC and with host computer (but application on host is not developed with LV, use a client socket to comunicate with PXI for reading data).
Error Log show alwayis the same error, and for my opionon, there is no relation for when the event occur, can be in any moment.
Application in pxi has some VI that are published as web service for diagnostic only, but there is no any interaction with user, (no keyboard and no mouse), it's a silent application, that read some encoder, calculate speed and aceleration, generate some output and send all data acquired via tcp/ip... 24 h/day.
Strange is that error position is always at 0x1924000, in all the error log!
Unfortunatly system is used all the day, and it's very far from office, so debug can be done only at specific day, when production is off... and internet is unavailable...
Enabling the debug mode, It's possible to have more information about the problem without changing the performance of the system?
Thank's for you help!
Nicola
Attachments:
img1.JPG ‏36 KB
img2.JPG ‏28 KB
img3.JPG ‏29 KB

Nivissvc dll error in LVRT

Hi all,
I am trying to use cRIO 9082 for image processing. When I try to deploy the vis , it shows deployed with errors. When I see the Error log it shows
LabVIEW: (Hex 0x627) The function name for the nivissvc.*:LV_AviMovieClose:C node cannot be found in the library. To correct this error, right-click the Call Library Function Node and select Configure from the shortcut menu. Then choose the correct function name.
04/09/2015 21:12:10.078 [error] LabVIEW: (Hex 0x627) The function name for the nivissvc.*:LV_AviMovieInfo:C node cannot be found in the library. To correct this error, right-click the Call Library Function Node and select Configure from the shortcut menu. Then choose the correct function name.
04/09/2015 21:12:10.098 [error] LabVIEW: (Hex 0x627) The function name for the nivissvc.*:LV_AviMovieOpen:C node cannot be found in the library. To correct this error, right-click the Call Library Function Node and select Configure from the shortcut menu. Then choose the correct function name.
04/09/2015 21:12:10.123 [error] LabVIEW: (Hex 0x627) The function name for the nivissvc.*:LV_AviMovieGetFrame2:C node cannot be found in the library. To correct this error, right-click the Call Library Function Node and select Configure from the shortcut menu. Then choose the correct function name.
04/09/2015 21:24:02.637 [error] LabVIEW: (Hex 0x627) The function name for the nivissvc.*:LV_AviMovieClose:C node cannot be found in the library. To correct this error, right-click the Call Library Function Node and select Configure from the shortcut menu. Then choose the correct function name.
What does these mean? Does this mean I cannot use AVI inside RT? or does this indicate any installation problems? It is urgent and any help is welcome

I too have been experiencing this problem, only with 8.2. I have
a built application that crashes semi-randomly on my development
machine - XP blames LVRT.DLL. I bundled the 8.2 LVRT.DLL into my
build as suggested, that didn't help. The application thus far is
just a fairly complicated GUI with no hardware being addressed (yet)
and no external libraries being called (yet).
Insight, anyone?
Thanx.

Application crashes in Windows 7 64bit made in Labview 2010 sp1 f2 with Fault module name%3A lvrt.dll%2C version 10.0.0.4033 and exception code c0000005

I build an application exe and then its installer along with run time environment.
The installers instals the application correctly but when I try to execute the application, I get an error that application has crashed and Windows must close it down or search for solutions online with this additional information for the crash.
Problem signature:
Problem Event Name: APPCRASH
Application Name: AGMS.exe
Application Version: 1.3.0.0
Application Timestamp: 4c24e8f5
Fault Module Name: lvrt.dll
Fault Module Version: 10.0.0.4033
Fault Module Timestamp: 4c9273f4
Exception Code: c0000005
Exception Offset: 00005310
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I am using labview 2010 sp1 32 bit on a 64-bit machine, with the following specs
Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533)
Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
System Model: Dell System XPS L502X
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz (8 CPUs), ~2.0GHz
Memory: 8192MB RAM
Available OS Memory: 8106MB RAM
Page File: 3457MB used, 12753MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
The exe /application runs fine on my PC but when I try to run it on another PC it crashes. The other PC has similar specs as given below
Operating System: Windows 7 Ultimate 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.140303-2144)
Language: English (Regional Setting: English)
System Manufacturer: LENOVO
System Model: HuronRiver Platform
BIOS: Default System BIOS
Processor: Intel(R) Core(TM) i3-2330M CPU @ 2.20GHz (4 CPUs), ~2.2GHz
Memory: 4096MB RAM
Available OS Memory: 4010MB RAM
Page File: 1359MB used, 6658MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 11
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
DxDiag Version: 6.01.7601.17514 32bit Unicode
I tried another machine, 64 bit of course, as I want to deploy my application on a 64bit PC, but still got the same problem.
This other machine was from HP, iCore 3 (4 CPUs) 2.2GHz, 4GB RAM and running Windows Professional 64 bit.
Now as I see it, it could be a Run-time environment mis-match error.
For this I tried installing a 64 bit LVRTE from NI, but still no sucess.
I checked DEP, for all 3 PCs and it was set to the following
Turn on DEP for essential Windows programs and services only (first option).
I am confused. I can not find a solution for this and it is really frustrating.

But I am assuming that when I make the installer, the 32-bit Run Time Engine is appened with the installer, as show below
Since from the picture you can see its including the support installers from '\Program Files (x86)\'
The application runs queries to fetch data from database in SQL server 2008, and for that I am using a Microsoft SQL Native Client 2008 R2 64 bit ( this is the only version that installs on either PC, even the one on which I developed my LV Application).
I am not using any driver, only toolkits for reports - and for that I un-checked the "Remove unused polymorphic VI instances" when making the executable, otherwise LV throws up an exception that share variable are not being included.
Yes I did reboot every time after I ran the installation.
Still getting the same error.

Lvrt.dll crash LV2010SP1

Problem Event Name:   APPCRASH
Application Name:   Test.exe
Application Version:   1.0.0.0
Application Timestamp:   4d2fa0d5
Fault Module Name:   lvrt.dll
Fault Module Version:   10.0.1.4002
Fault Module Timestamp:   4d2fb3a1
Exception Code:   c0000005
Exception Offset:   007487b7
OS Version:   6.1.7600.2.0.0.256.48
Locale ID:   1033
This is LabVIEW 2010 SP1 on Windows 7.
Maybe it has something to do with "Call By Reference" , but not sure.

Strange, I would also appreciate any updates on a solution. I can run my application for several days as well and then the system gives me the error. I have not checked my DEP settings, but will do so. I was leaning towards a problem with resources since I am running for several days - I thought maybe the memory or cpu usage was a problem.
I am using Windows 7, LabVIEW2013, SP1 64 bit application.
Is there any reasonable way to recover from this crash programmatically since it is a Windows error?
Problem signature:
Problem Event Name:                        APPCRASH
Application Name:                             Avionic_Communication.exe
Application Version:                           5.0.0.2
Application Timestamp:                     52d9885e
Fault Module Name:                          lvrt.dll
Fault Module Version:                        13.0.1.4018
Fault Module Timestamp:                  52d99503
Exception Code:                                  c0000005
Exception Offset:                                0000000000bb7e80
OS Version:                                          6.1.7601.2.1.0.256.48
Locale ID:                                             1033
Additional Information 1:                  56fb
Additional Information 2:                  56fb6f9c2aae0ddbb77d8c94b1041558
Additional Information 3:                  848b
Additional Information 4:                  848b2abc34bf08ac556f274cd9d77734
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

LVRT.DLL load address: 0x02110000

Hi,
I have two PXI-8108 with the same aplication. Both PXI have the same problem. When I run the software or sometime after begun the PXI reboot due to system error. At one of them return a log message LVRT.DLL load address: 0x02110000.
I already reinstall the Labview RT 2011 at PC and PXI.
What else can I do?
Thanks

Hi Schimitz,
I note you are using LabVIEW 2011, have you ever install any LabVIEW install LabVIEW 2011 f2 patch?
http://joule.ni.com/nidu/cds/view/p/id/2657/lang/en
If you don´t do it yet i recommend do it and after reinstall RT software at PXI-8108.
Best regards,
Abel Souza
Applications Engineering
NI Brazil
Abel Souza
Engenheiro de Aplicações
National Instruments Brasil

Problema con lvrt.dll

Buenas tardes, tengo una aplicación para monitorear unas máquinas de confección por medio de una red RS-485/TCP-IP y en el computador en donde tengo corriendo el supervisor a veces me muestra un mensaje de error en el .exe refiriendose al lvrt.dll. Busque en el PC e incontré esta librería repetida, una de una versión vieja de Labview (7.0) y la de esta versión (7.1), entonces eliminé la vieja, pero el Error sigue apareciendo. ¿Qué podría ser?
Adjunto las imagenes del error.
Muchas gracias.
Attachments:
Error 1.JPG ‏160 KB
Error 2.JPG ‏136 KB

Buenas tardes, tengo una aplicación para monitorear unas máquinas de confección por medio de una red RS-485/TCP-IP y en el computador en donde tengo corriendo el supervisor a veces me muestra un mensaje de error en el .exe refiriendose al lvrt.dll. Busque en el PC e incontré esta librería repetida, una de una versión vieja de Labview (7.0) y la de esta versión (7.1), entonces eliminé la vieja, pero el Error sigue apareciendo. ¿Qué podría ser?
Adjunto las imagenes del error.
Muchas gracias.
Attachments:
Error 1.JPG ‏160 KB
Error 2.JPG ‏136 KB

Application causes Windows fault in lvrt.dll among others...

I have an application that will occasionally crash due with a Windows error. It states that the error is in the lvrt.dll file. It lists 80 different modules in the technical information area of the warning. I have tried to reinstall all NI hardware and software and the error will still occur. it always happens at the same point in the software if it is goign to happen. This occurs right after pushing the start button the first time through the software. If I reboot the PC, the software will normally run fine for a while. Does anyone know what may be causing this problem? I have included the main application. I am running this application as an executable on the PC in question. The PC is Windows XP SP2, with a Pentium II 863 MHz and 512Mb of RAM.
Thanks,
Craig

James,
When the problem occurs, it happens at the same time, once you double click on the executable.  I was doing some testing last night, it seemed better once I reset the compact daq device in Max.  Do you think it has anything to do with the Daq device and how it sets up?  Is there a way of programatically reseting the the daq device at startup (right now daq (digital and analog) start right away once the program is executed).
I looked ath the error log file that was created and it points the ApplLib - don't know if this could help.  The system has just left to the customer for a "demo" but will be back in a few days.
Sci-Mech

LabVIEW Run-Time Crash (2009) lvrt.dll

Hello,
I am currently experiencing a problem with an application built with LabVIEW 2009. At random periods (often not more than once or twice a week when using the application regularly) I get a Windows error referencing lvrt.dll as the culprit. I am having a hard time troubleshooting because of the scarcity of the problem, as well as the random nature (appearing in completely separate parts of the application, does not seem to be associated with any particular module of the code).
A little background- I have inherited the application maintenance, which has gone through many different versions of LabVIEW. I implemented the code into LabVIEW 2009 from 8.6, which is when the error began to appear. At that time no change was made to the source code itself, just merely built using 2009 rather than 8.6.
I apologize for the somewhat vague information; unfortunately this is all I have after working on this issue for weeks. If anyone has any suggestions or similar experience your advice would be greatly appreciated!
Thanks

Hello Again Sean, thanks for your help.
I am running 2009 SP1.
There are other DLLs called throughout the code, but not any specific calls seem to cause the crash. Likewise, as the crash will occur randomly throughout all of the software I suspect it is not in the code itself (i.e. this application consists of nearly 1000 VIs. The crash has occurred while running various parts of the software, so it can't be traced to any particular party of the code via debug mode, highlight execution, etc).
I have attached a screen shot of the error message I receive. Any other thoughts would be greatly appreciated.
Attachments:
error2.JPG ‏52 KB
error1.JPG ‏26 KB

Guide to overcome hal.dll error - disk error & other errors.

Okay to start off with - guide for installing bootcamp.
DISCLAIMER:
I take no responsibility at all - whatsoever for any damage the following steps cause to anything. If you follow this guide and then are annoyed at me in any way - don't be - you followed these steps knowing they could be dangerous to your hard drive / computer / sanity / etc. That said - good luck & these steps should work for everyone.
requirements: XP SP2 CD & a copy of parallels would be useful. Also a non-apple usb keyboard for step 1 if the apple one doesn't work during xp bootup.
1. First try the usual bootcamp assistant method. Insert the xp disk, in the setup make sure you format the drive to NTFS (not quick). If you don't get this option - skip to step 3.
2. Reboot and hopefully everything will go without a hitch. If it doesn't and you get a hal.dll error or any other kind of error go on to the next step.
3. Boot up mac os x. Install parallels desktop.
4. Insert your windows xp sp2 cd.
5. Create a new virtual machine using a virtual hard drive saved in your documents folder somewhere.
6. Configure it so that the bootcamp drive is added as an extra secondary drive in the virtual machine. (Little plus button down at the bottom).
7. Install XP onto the virtual machine - don't activate or anything, just get to the desktop stage as fast as possible.
8. Parallels will have already asked for your password to dismount the boot camp drive.
9. Double click my computer in the virtual machine, then hold down ctrl+shift and click on the BOOTCAMP partition in the my computer window.
10. Click format.
11. Select NTFS as file format, check enable compression - do not check quick format.
12. Wait till its finished and then power down the virtual machine.
------- The following steps are taken from http://communities.vmware.com/thread/114529 and were written by MandarMS from the vmware forums. I have edited the guide a little - (you'll see where). Thanks and all credit to MandarMS.----
13. (James: Close parallels)
14. Quit all applications in Host Mac OS X
15. Open Terminal utility from Macintosh HD : Applications : Utilities folder.
16. Key-in the following command
$ sudo fdisk /dev/rdisk0
17. Preferably take the screenshot of the output or Note down the output (for restoring MBR).
18. Key-in the following command
$ sudo fdisk -e /dev/rdisk0
setpid 3
Choose 07 (as the partition type)
write
Y
Restart your Mac System
(James: EDIT - BELOW IS AN EXAMPLE OF THE OUTPUT OF THE PROGRAM IF YOU ARE UNSURE OF WHAT TO TYPE IN WHERE - This confused me at first but really helped in the end - James)
For more details please check the example shown below:
$ sudo fdisk -e /dev/rdisk0 (this will help to change the MBR)
$ fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> setpid 3 (Enter “setpid 3” press enter key)
Starting Ending
#: id cyl hd sec - cyl hd sec start - size
*3: 0B 1023 254 63 - 1023 254 63 1127792680 - 337356448 Win95 FAT32L
Partition id ('0' to disable) 0 - FF: [C] (? for help) 07 (Enter 07 Partition table)
fdisk:*1> write (enter “write” press enter key, This will change the MBR)
Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] Y (Press Y to modify changes)
Writing MBR at offset 0.
$ fdisk: 1> exit (enter “exit”, press enter key)
19. Restart your Mac System
------ Back to me again.
20. Welcome back - your drives have just been fixed. Reboot again and insert the windows xp sp2 cd. Hold down option at startup and boot from the cd.
21. Go through the setup again - this time don't do anything to the drives when it asks you to format.
22. wait...
23. It'll reboot......
24. It'll install..... if it doesn't - skip to step 26
25. Welcome to windows, install your drivers and reboot a couple more times. You're good.
26. (it didn't work... you got the hal.dll error or something similar) Boot up mac os x again and launch parallels.
27. Start up the virtual machine - open up BOOTCAMP in my computer.
28. Click view - folder options
29. View types > make sure you can see hidden files and folders, view system files and etc.
30. Right click boot.ini and click properties
31. Uncheck read-only.
32. Click okay - open boot.ini in notepad.
33. If you're on a mac with 2 partitions: 1 mac hd, 1 bootcamp, delete everything in the boot.ini file and copy and paste the following into it:
\[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
\[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
Obviously change the name to suit. Save it and reboot - you should be good to go now.

Hi. Your bootcamp drive should be drive C. It shouldn't matter what drive letter it is really, you make the virtual machine disk as a virtual disk saved in your documents folder and hook it in to use your physical bootcamp drive.
Ensure you've typed in the correct command and correct password. Press enter after you type in the password. You won't see it as you type it in, and you may need to wait some time afterwards before you'll see the next prompt. Leave it 2 minutes.
Sorry I've been abroad.. hope you have it worked out by now anyway mate.

Lvrt.dll Error

Similar Messages

Maybe you are looking for