An Unexpected Error 768 Occurred At Line 5218
be down. Please try the request again. Your cache administrator is webmaster. Generated Thu, 29 Sep 2016 23:48:45 GMT by s_hv972 (squid/3.5.20)
TechSpot RSS Get our weekly newsletter Search TechSpot Trending Hardware The Web Culture Mobile Gaming Apple Microsoft Google Reviews Graphics Laptops Smartphones CPUs Storage Cases Keyboard & Mice Outstanding Features Must Reads Hardware Software Gaming Tips & Tricks Best Of Downloads Latest Downloads Popular Apps Editors Picks Device Drivers Product Finder New Releases New PC Games Laptops Smartphones Routers Storage Motherboards Monitors Forums Recent Activity Today's Posts News Comments TechSpot Forums Forums TechSpot Core Networking Today's Posts Error when installingWindows ByJonostra Dec 15, 2007 Hello, to start with i am not a wiz with computer hardware.. I will try to explain the problem as good as possible. oke, so.. http://answers.microsoft.com/en-us/windows/forum/windows_xp-windows_install/unexpected-error-32769-in-line-5218/579cedd6-fdd0-48a3-a499-2e7eba83edf6 two months ago my motherboard stopped working for some reason. i dilivered it to my dealer, and they placed a new motherboard inside. Once done, i connected my old HDD and for some reason it did not work. Although i kept trying, ending up with some part of the HDD burned.. So i thought it was the fault of the HDD, and decided to buy a new one. Now i have a pretty WD http://www.techspot.com/community/topics/error-when-installing-windows.94497/ Raptor X connected, and tried to install XP once again. This time everything goes well. Windows starts detecting the hardware as usual with the install CD inside when i reboot the comp, but it doesn;t finish. At the same point every time i get this error msg: An unexpected error (769) occurred at line 5218 in D:\nt\base\boot\setup\setup.c. Could this be a problem caused by a different part then the HDD? This is an expensive HDD, and i don;t want to blow this one as well.. I googled the error, and the only thing i found was another thread on this forum, and thats how i got here. Before i start to recover or zero my HDD, i would like to ask if some1 here has an idea if this is infact a problem caused by the HDD itself or not. And of course, What to do? Thanks in advance, Jo. Dec 15, 2007 #1 Rik Banned Posts: 3,814 Hi Jonostra and welcome to TechSpot. Windows XP (assuming that's what you have as you haven't actually said) needs to be reinstalled when the mobo (motherboard) is changed. At the very least it will need a windows repair done on it. Dec 15, 2007 #2 Jonostra TS Rookie Topic Starter Hi Rik, thanks for your fast respond. I have trie
diagnostic information are stored in: A user error log that contains error message information. Generally, these messages contain information on actions you may need to take. The default file is ReplicationApplyOrdering8ReplicationApplyOrdering7. For more information on modifying the location of the user error log, see "Modifying informational messages" in the Oracle TimesTen In-Memory Database Operations Guide. A support log containing everything in the user error log plus information that may be useful for TimesTen Customer Support. The default file is ReplicationApplyOrdering6ReplicationApplyOrdering5. For more information on modifying the location of the support log, see "Modifying informational messages" in the Oracle TimesTen In-Memory Database Operations Guide. An invalidation file containing diagnostic information when TimesTen invalidates a database. This file provides useful troubleshooting information for TimesTen Customer Support. The invalidation file is created and named based on the value specified by the ReplicationApplyOrdering4 connection attribute. This connection attribute is not a file name. For example on Linux platforms, if the ReplicationApplyOrdering3 connection attribute is ReplicationApplyOrdering2, the actual invalidation file name has a suffix, ReplicationApplyOrdering1, ReplicationApplyOrdering0. For more information on the ReplicationApplyOrdering9 connection attribute, see "DataStore" in the Oracle TimesTen In-Memory Database Reference. Note: Not all error numbers are currently in use. Retrieving errors and warnings In JDBC, the native error code and message can be retrieved as shown in this example: Example 1-1 Native error code and message retrieval in JDBC private static void printSQLExceptions(SQLException e) { while (e != null) { System.out.println("SQLState: " + e.getSQLState()); System.out.println("Message : " + e.getMessage()); System.out.println("Vendor : " + e.getErrorCode()); e.printStackTrace(); e = e.getNextException(); System.out.println(""); } e.printStackTrace(); } . . . try { // JDBC method calls here } catch (SQLException ex) { ex.printSQLExceptions(); } In ODBC, the native error code and message can be retrieved with the ReplicationApplyOrdering8 function, as shown in the following example: Example 1-2 Native error code and message retrieval in ODBC #define MSG_LNG 512 SQLCHAR szSqlState[MSG_LNG]; /* SQL state string */ SQLINTEGER pfNativeError; /* Native error code */ SQLCHAR szErrorMsg[MSG_LNG]; /* Error msg text buffer pointer */ SQLSMALLINT pcbErrorMsg; /* Error msg text Available bytes */ SQLRETURN ret = SQL_SUCCESS; while ( ret == SQL_SUCCESS ||