- This topic has 23 replies, 3 voices, and was last updated 19 years, 10 months ago by
.
-
Posts
-
Well, sadly I re-installed, etc etc at the work machine and had the exact same results and error messages. The big differences between the work and home machines are that the work machine is Win2k and IE 5.5 and the home machine is WinXP and IE 6…
All the same errors and problems as before… 🙁
WinXP and IE 6? That’s what *all* our development machines run. If there’s any config that will work, it’s that one. On the first platform it might have been a win2k issue, but on XP it makes no sense. One question, is your XP machine updated with the lastest patches (SP2) and fixes from Microsoft? I know all ours are, so if your isn’t that could be a difference worth investigating.
From my previous post:
>Once you get the page so that it won’t resync, even when manully requested, can you click on the source tab and paste it here?Scott,
I’m sorry… MY HOME OFFICE machine (with XP and IE6) works *perfectly*. The Win2K machine with IE 5.5 doesn’t..
From your previous post:
>Once you get the page so that it won’t resync, even when manully requested, can you click on the source tab and paste it here?<%@ page language=”java” import=”java.util.*” pageEncoding=”UTF-8″%>
<%
String path = request.getContextPath();
String basePath = request.getScheme()+”://”+request.getServerName()+”:”+request.getServerPort()+path+”/”;
%><!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01 Transitional//EN”>
<html>
<head>
<base href=”<%=basePath%>”><title>My JSP ‘MyJsp.jsp’ starting page</title>
<meta http-equiv=”pragma” content=”no-cache”>
<meta http-equiv=”cache-control” content=”no-cache”>
<meta http-equiv=”expires” content=”0″>
<meta http-equiv=”keywords” content=”keyword1,keyword2,keyword3″>
<meta http-equiv=”description” content=”This is my page”><!–
<link rel=”stylesheet” type=”text/css” href=”styles.css”>
–>
</head><body>
This is my JSP page. <br>
</body>
</html>I’m sorry… MY HOME OFFICE machine (with XP and IE6) works *perfectly*. The Win2K machine with IE 5.5 doesn’t..
OK, now that restores my view of the world somewhat. 🙂
Based on the home machine configuration, it’s likely a difference with IE 5.5. While the APIs we use were available then, they might work differently in IE 6. Would upgrading your browser to IE 6 on your Win2K installation be an option? If so, that would provide a great test for us, compatibility-wise. Unfortunately, we don’t have any machines with IE 6 still in the lab.
Unfortuately if I upgrade to IE 6 and something breaks, I will be held responsible for it and since this is a client site and I’m a consultant to them I’d probably be dismissed (yea.. they’re that antsy).
Dave,
I understand that, completely; been there. OK, we’ll have to see if we can dig up a Win 2K machine with IE 5.5 to test against. Right now though, I did determine that that configuration has not been tested, so likely we’re seeing an incompatibility between what we expect the underlying COM libraries to do (IE 6) and what they do in IE 5.5. I suppose at the present time there is no good workaround for you on that platform other than simply using the source view and the design / preview views just for “looking but not touching”. I’ll see if we can find out anything further later.
But, at least you’re up and running well on your home office setup, and you can use the same license (since it’s for *you*, not a particular machine) in both places. Maybe you can save the hardcore visual editing for “homework”? 😉
Dave,
Well, it didn’t take long to get confirmation. IE6 is required for the designer to work on Windows 2K:
http://www.myeclipseide.com/PNphpBB2+file-posting-mode-editpost-p-40601.htmlActually, IE6 is required on any platform, but that’s definately the issue you’re experiencing on your work PC. At least we know now.
Dave,
One more thing. Please note that the install still includes the “MyEclipse Classic JSP Editor” so you should be able to right-click and use Open With… > MyEclipse ‘Classic’ JSP Editor on the IE 5.5 machine, if you’d rather not see the design stuff that won’t work with that version of the browser.
