Re: [SLUG] Compatibility Issues with Windows64
Just got some more details. There are apparently 2 concerns: One is that the Windows64 file system is yet another variant of NTFS (well, why not?) and may not be compatible with Linux. I think the concern here is in file transfer between systems, and I think they are talking about the samba-based windows network (a second option), so I was able to advise that the file system is transparent in file transfers from the windows workstation to the Linux server. The second is that the files are not compatible between OpenOffice and MS-Office. Which has precisely zip to do with 64 bit! I was able to clarify that as well. Regards, Edwin Humphries Mobile: 0419 233 051 Ironstone Technology Pty Ltd P. O. Box 423, Kiama, NSW, 2533 Phone: +61 (0)2 4233 2285 Facsimile: +61 (0)2 4233 2299 Web: http//www.ironstone.com.au *** This email is intended for the named addressee/s only and may contain confidential or privileged information. If you are not a named addressee please delete the message and notify the sender. *** Daron Barndon wrote: Edwin, I work with fedgov clients here in canberra and I have heard nothing about this. Do you have more information? Sounds a bit dodgy... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Humphries Sent: Thursday, 5 May 2005 2:41 PM To: SLUG Subject: [SLUG] Compatibility Issues with Windows64 We're quoting on a Linux thin-client network in a government-funded establishment. One of the comments (third-party so I haven't been able to check background) is that Federal Government bodies are concerned that there are Linux compatibility issues with upcoming 64-bit Windows. I don't see how this is relevant, and I suspect it's a crock (another threatened Windows quasi-guru), but before I go in to bat, has anyone heard of this? -- Regards, Edwin Humphries Mobile: 0419 233 051 Ironstone Technology Pty Ltd P. O. Box 423, Kiama, NSW, 2533 Phone: +61 (0)2 4233 2285 Facsimile: +61 (0)2 4233 2299 Web: http//www.ironstone.com.au *** This email is intended for the named addressee/s only and may contain confidential or privileged information. If you are not a named addressee please delete the message and notify the sender. *** -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html # This e-mail, including all attachments, may be confidential or privileged. Confidentiality or privilege is not waived or lost because this e-mail has been sent to you in error. If you are not the intended recipient any use, disclosure or copying of this e-mail is prohibited. If you have received it in error please notify the sender immediately by reply e-mail and destroy all copies of this e-mail and any attachments. All liability for direct and indirect loss arising from this e-mail and any attachments is hereby disclaimed to the extent permitted by law. # -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Compatibility Issues with Windows64
Edwin Humphries wrote: Just got some more details. There are apparently 2 concerns: One is that the Windows64 file system is yet another variant of NTFS (well, why not?) and may not be compatible with Linux. I think the concern here is in file transfer between systems, and I think they are talking about the samba-based windows network (a second option), so I was able to advise that the file system is transparent in file transfers from the windows workstation to the Linux server. 1. Even for local access, you might be able to use this driver with ndiswrapper. Work asking on the ndiswrapper mailing list. The second is that the files are not compatible between OpenOffice and MS-Office. Which has precisely zip to do with 64 bit! I was able to clarify that as well. Hehe. 1. Try grabbing various PPTs and DOCs from Microsoft's web site, and opening them in OOo 1.1 - particularly with MS Fonts or the Agfa equivalents from RHEL installed. That'll give them a good idea of compatibility. 2. OOo 2, (say from FC4 test) implements nested tables, very large spreadsheets, and other useful things 1.1 didn't do for MS Office compatibility. Cheers, Mike -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Compatibility Issues with Windows64
On Thu, 2005-05-05 at 19:03 +1000, Mike MacCana wrote: Edwin Humphries wrote: Just got some more details. There are apparently 2 concerns: One is that the Windows64 file system is yet another variant of NTFS (well, why not?) and may not be compatible with Linux. I think the concern here is in file transfer between systems, and I think they are talking about the samba-based windows network (a second option), so I was able to advise that the file system is transparent in file transfers from the windows workstation to the Linux server. 1. Even for local access, you might be able to use this driver with ndiswrapper. Work asking on the ndiswrapper mailing list. I don't know what would have given you that impression. NDIS stands for Network Driver Interface Specification. NDIS is a specific subset of the windows driver system that deals with drivers for networking adapters. That said, there has been some code from ReactOS that successfully wraps the ntfs.sys file from an MS Windows install to provide full read-write access to NTFS. I doubt that will work unmodified with the 64 bit equivalent, but may not lag too far behind it. J. -- Jan Schmidt [EMAIL PROTECTED] -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Compatibility Issues with Windows64
Edwin Humphries wrote: Federal Government bodies are concerned that there are Linux compatibility issues with upcoming 64-bit Windows. Uhhh, I'd personally be more worried about the absolutely certain incompatabilities that exist between win64 and winXP/2k. It's so hard to believe that the world is going to willingly switch to win64 when the vast majority of 3rd party hardware currently in existance doesn't work with it. In many ways, it's like Linux was like back in the 90s. Trent -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Compatibility Issues with Windows64
Jan Schmidt wrote: On Thu, 2005-05-05 at 19:03 +1000, Mike MacCana wrote: Edwin Humphries wrote: Just got some more details. There are apparently 2 concerns: One is that the Windows64 file system is yet another variant of NTFS (well, why not?) and may not be compatible with Linux. I think the concern here is in file transfer between systems, and I think they are talking about the samba-based windows network (a second option), so I was able to advise that the file system is transparent in file transfers from the windows workstation to the Linux server. 1. Even for local access, you might be able to use this driver with ndiswrapper. Work asking on the ndiswrapper mailing list. I don't know what would have given you that impression. NDIS stands for Network Driver Interface Specification. NDIS is a specific subset of the windows driver system that deals with drivers for networking adapters. Oops. I meant captive NTFS. Both Captive NTFS and ndiswrapper are implementations of the NT kernel API which allow you to run x86 FS/NDIS drivers respectively on x86 Linux. I don't know if an AMD64 version of Captive NTFS exists, but I don't see why it wouldn't be possible. I think the ReactOS stuff is a port of Captive NTFS for Linux. Mike -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
[SLUG] Compatibility Issues with Windows64
We're quoting on a Linux thin-client network in a government-funded establishment. One of the comments (third-party so I haven't been able to check background) is that Federal Government bodies are concerned that there are Linux compatibility issues with upcoming 64-bit Windows. I don't see how this is relevant, and I suspect it's a crock (another threatened Windows quasi-guru), but before I go in to bat, has anyone heard of this? -- Regards, Edwin Humphries Mobile: 0419 233 051 Ironstone Technology Pty Ltd P. O. Box 423, Kiama, NSW, 2533 Phone: +61 (0)2 4233 2285 Facsimile: +61 (0)2 4233 2299 Web: http//www.ironstone.com.au *** This email is intended for the named addressee/s only and may contain confidential or privileged information. If you are not a named addressee please delete the message and notify the sender. *** -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
Re: [SLUG] Compatibility Issues with Windows64
Edwin Humphries wrote: We're quoting on a Linux thin-client network in a government-funded establishment. One of the comments (third-party so I haven't been able to check background) is that Federal Government bodies are concerned that there are Linux compatibility issues with upcoming 64-bit Windows. What do you mean? Dual booting? AMD64 (and Intel AMD64 clones) bit machines use Grub and can dual boot with WIndows just like a 32 but machine. There is no Windows XP for Itanium anymore, but if you have an old unsupported copy, I believe ELILO (used on Itaniums) can dual boot with that too. Mike I don't see how this is relevant, and I suspect it's a crock (another threatened Windows quasi-guru), but before I go in to bat, has anyone heard of this? -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
