RE: Problems while creating/running apps for Vista
CubicDesign wrote: Subject: Re: Problems while creating/running apps for Vista As I said, I don't use an installer (actually I am using WinRAR as installer but this is not a real installer) and I don't really need one. You might want to give InnoSetup a try. It's simple, it's not MSI, it's written in Delphi, compresses better then WinRar (7zip), gives you a professional look, allows you to install your software wherever you want, allows more options (like running a small helper program to set up file associations or whatever). I do not know if this kind of installer will be detected by Vista's heuristics. All my installers are called setup-something.exe. The only thing that is really not working on Vista (but worked on XP) is associating the program with some file types (like *.SQ). I don't know if it will be possible to do this anymore without having administrator rights. This is an important feature for my users because 1) they are not advanced users (not even medium) and 2) they have to process hundreds or thousands of files per day, files that are spread in many many folders with difficult names (name of the folder is generated by a machine) and that must be 'mixed' together. I can't help you with this one, but I'll confirm that Vista did change something related to the way file associations work. I think the theory was that applications can change file associations too easily so they've set something up so the user has more control. Again - good theory, more work for us :-) I know nothing more about this because I had no need to change file associations. Or maybe my file associations just worked because I was doing them from the setup.exe - so I had Administrative privileges. What I'm saying is that your associations are failing not because you don't have administrative rights but because you're doing the XP way, not the Vista way. It might be time for that extra computer so you can run Vista (it's cheaper to buy a new PC + Vista OEM - you can't run OEM in a virtual machine and you need to buy a retail copy of Vista Ultimate or Vista Business for a VM - or get a MSDN OS Subscription). -- Cosmin Prund ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
Re: TXMLDocument and ampersand
Enclose it in a CDATASection. Not sure it would change anything except make the XML even less human readable. My goal is to have the XML the most human readable as possible, with best indentation. -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
Re: TXMLDocument and ampersand
nodexamp;#13;amp;#10;y/node That's not what Francois wants. He wants this: nodex#13;#10;y/node Right ! The XML serializer, though, doesn't normally bother with character entities for normal printable characters like carriage return and line feed. Instead, it outputs this: nodex y/node Correct ! I don't usually see XML serializers that bother generating CDATA sections. Instead, they just use character entities to encode whatever characters aren't in the output encoding. If the output encoding is UTF-8 or UTF-16, then nothing gets encoded except ampersand, greater-than, less-than, and apostrophe. Frequently, when a software do some character encoding for special characters, there is mechanism to allow the delimiters to be inserted in the data stream. Think about Delphi: the quote is used to delimit strings. To put one quote in a string, anyone know that it is enough to duplicate it. Other software use similar mechanism such as backslash something. What I'm looking is a similar mechanism in TXMLDocument (or MSXML which is behind TXMLDocument). Maybe it is possible to override and customize the serializer ? -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
Re: Save IDE bookmarks in Delphi 7
Hmmm. Too bad. :( I had problems with Delphi 2005. For example the help system didn't worked at all in my computer. I heard that they fixed it in the first update, but only partially. I will wait for the second update then maybe I will try that Delphi again. Until then I had a 'system' to save the bookmarks: for big projects, before closing the IDE I put an 'error' (random text) in the PAS file where the most important bookmarks are. Next time I open the IDE and compile, it will send me right where the 'error' is, so I can re-insert the bookmarks (and delete the 'error'). Complicated, I know, but I use bookmarks allot. Jeremy North wrote: Unfortunately it requires D2005. That was when Borland started persisting them. You could try Jeremy North's bookmark add-in. I only see versions for Delphi 2005 and Delphi 2006, but you might be able to make it work with Delphi 7, too. ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
RE: Problems while creating/running apps for Vista
Thanks for the Info! Your suggestion was exactly right. Vista no longer allows anyone (or anything) to write to the root of C: Changing the Net Dir to C:\Temp fixed the problem. One puzzle for me: I setup the BDE so that anyone could use it, but whenever a new user tries to run the BDE, it fails and I have to create a new Idapi32.Cfg file for that user. When I look in the BDE folder, I only see one copy of this file, so I don't know where the other copies go. Once I do that, the user can run my program without problemsNew OS's are such fun...;-/ Tom Nesler -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cosmin Prund Sent: Monday, July 23, 2007 11:14 AM To: Borland's Delphi Discussion List Subject: RE: Problems while creating/running apps for Vista I think you need to change the temp folder for the installation, after the BDE has installed. It goes something like this. You go to Control Panel, open the applet, change the temp folder to something you know BDE has the right to write (I used C:\Temp and gave everyone permission to write there). You click whatever button is required to apply the change. The control panel applet hangs. You close it from Task Manager and subsequently your BDE applications work :-) This worked for me. It's in a working part of a program so it hasn't been touched for a very, very long time (if it aint broke don't fix it). It's now time to change as I don't like the instructions I just gave. -- Cosmin Prund -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nesler, Thomas J Sent: 23 iulie 2007 16:26 To: Borland's Delphi Discussion List Subject: RE: Problems while creating/running apps for Vista Hello! Thanks for the tips! I was wondering, does anyone know about a website or links to a website that chronicles problems with running applications on Vista? I am trying to run an old BDE/Paradox App and I am getting the AppCrash error but no details as to what exactly is going wrong. The MSI that installed the BDE ran fine and I can run the BDEAdmin program Ok. Tom Nesler -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Irwin Scollar Sent: Friday, July 20, 2007 10:41 AM To: delphi@elists.org Subject: Problems while creating/running apps for Vista I had a number of problems in porting my apps to Vista. 1) Help files for all applications had to be translated to HTML (.chm) format, since Vista doesn't support the old (.hlp) format without problems even when the updated version is downloaded and installed by the user. 2) Rights have to be set correctly by the installation program on the installation directory if anything is to be written there by non-administrative users. 3) Nothing must touch anything but the Current_User key in the registry except at installation time by a user with administrative rights. 4) Ini files must only be created and written to on directories to which a non-administrative user has appropriate rights. Nothing can be written to the Windows directory and to the partition on which it resides without Vista either objecting or blocking the write. The ($SETPEFLAGS $20} option for addressing more than 2GB memory in the .dpr under D7 caused a crash under Vista if the physical address space is greater than 2GB. Vista x64 has it's own problems, primarily if pointers are typecast to integer and the machine has more than 2GB of physical memory. Cardinals had to be used instead for pointer arithmetic. But this applied to XP x64 too. There are lots more, but those were the main changes I had to make in my apps in Delphi 7. I didn't attempt to get Delphi 7 itself running under Vista. If anyone has any experience with that, please describe your experience, especially if you used MS's KB932246 two compatibility routines for x32 and x64 Vista systems. Irwin Scollar ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
Moderator: BDE Installation Under Vista - please take to Delphi-DB
I've approved some of the Vista discussions that have had the BDE in them, but can we please take any further discussion to the Delphi-DB List where they belong - thanks :) - Glenn ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
Re: Problems while creating/running apps for Vista
What I'm saying is that your associations are failing not because you don't have administrative rights but because you're doing the XP way, not the Vista way. Great! This is a good point from where to start. Thanks allot. Of course, I will need Vista first :( you can't run OEM in a virtual machine But I suppose I can install Vista on a separate partition. Then I can use a booter program to choose between XP and Vista. Right? Cosmin Prund wrote: CubicDesign wrote: Subject: Re: Problems while creating/running apps for Vista As I said, I don't use an installer (actually I am using WinRAR as installer but this is not a real installer) and I don't really need one. You might want to give InnoSetup a try. It's simple, it's not MSI, it's written in Delphi, compresses better then WinRar (7zip), gives you a professional look, allows you to install your software wherever you want, allows more options (like running a small helper program to set up file associations or whatever). I do not know if this kind of installer will be detected by Vista's heuristics. All my installers are called setup-something.exe. The only thing that is really not working on Vista (but worked on XP) is associating the program with some file types (like *.SQ). I don't know if it will be possible to do this anymore without having administrator rights. This is an important feature for my users because 1) they are not advanced users (not even medium) and 2) they have to process hundreds or thousands of files per day, files that are spread in many many folders with difficult names (name of the folder is generated by a machine) and that must be 'mixed' together. I can't help you with this one, but I'll confirm that Vista did change something related to the way file associations work. I think the theory was that applications can change file associations too easily so they've set something up so the user has more control. Again - good theory, more work for us :-) I know nothing more about this because I had no need to change file associations. Or maybe my file associations just worked because I was doing them from the setup.exe - so I had Administrative privileges. What I'm saying is that your associations are failing not because you don't have administrative rights but because you're doing the XP way, not the Vista way. It might be time for that extra computer so you can run Vista (it's cheaper to buy a new PC + Vista OEM - you can't run OEM in a virtual machine and you need to buy a retail copy of Vista Ultimate or Vista Business for a VM - or get a MSDN OS Subscription). -- Cosmin Prund ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
RE: Problems while creating/running apps for Vista
I can't help you with this one, but I'll confirm that Vista did change something related to the way file associations work. I think the theory was that applications can change file associations too easily so they've set something up so the user has more control. Again - good theory, more work for us :-) I know nothing more about this because I had no need to change file associations. Or maybe my file associations just worked because I was doing them from the setup.exe - so I had Administrative privileges. What I'm saying is that your associations are failing not because you don't have administrative rights but because you're doing the XP way, not the Vista way. I use Inno setup to install my products. I set the associations in the installer, and that works fine under Vista. Regards Sean Cross IT Systems Development Manager Catalyst Risk Management PO Box 230 50 Dalton St Napier 4140 DDI: 06-8340362 mobile: 021 270 3466 Visit us at http://www.catalystrisk.co.nz/ Offices in Auckland, Napier, Wellington Christchurch Disclaimer: The information contained in this document is confidential to the addressee(s) and may be legally privileged. Any view or opinions expressed are those of the author and may not be those of Catalyst Risk Management. No guarantee or representation is made that this communication is free of errors, viruses or interference. If you have received this e-mail message in error please delete it and notify me. Thank you. ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
RE: Problems while creating/running apps for Vista
Hi All, The issues with the program files folder makes me think that this is the death of the program files location for small developers such as myself. I find it useful and very convenient to store my programs and data in the one location. My programs are small and my data is an integral part of the program, therefore it makes sense to me to have them in the same location, and makes it easier for my users (who know less about computers than most) to keep track of their stuff. I can't help think Microsoft are less interested in protecting the end-user than lining their own pockets. If Vista is capable of detecting an old-style setup program and create the virtual program files folder, then surely it's capable of displaying the UAC or whatever it's called to ask for confirmation that overwriting a program is ok. You are about to replace a program stored in the program files folder, is this ok? Cheers, Chris. ___ Delphi mailing list - Delphi@elists.org http://www.elists.org/mailman/listinfo/delphi
